'tablesaw_type' is not a supported key. 'tablesaw_persist' is not a supported key.

I take it back: it does not work with Drupal 10.3.0, though it could be related to updates to Symfony, such as a recent update of symfony/validator (v6.4.8) to (v6.4.9).

The fix for this was committed to both the 8.x-1.x branch and 2.x branches. See https://git.drupalcode.org/project/responsive_tables_filter/-/commit/eaf...

A release for 2.x is available that includes this change. 8.x-1.x does not yet have a release that includes this fix.

Here's a patch for the 1.x release if anyone needs it.

@mark_fullmer The problem is that while the 2.x branch fixes this issue, it introduces a new one: https://www.drupal.org/project/responsive_tables_filter/issues/3460761 🐛 Module causes javascript problems in edit form Active . So I had to revert to the 8.x-1.x branch, which does not include this fix.

@mortona2k Your patch is empty. Can you check it and try reposting?

Not sure what happened, but it's just from the merge request: https://git.drupalcode.org/project/responsive_tables_filter/-/merge_requ...

So I had to revert to the 8.x-1.x branch, which does not include this fix.

The 8.x-1.x branch does include this fix. See https://git.drupalcode.org/project/responsive_tables_filter/-/blob/8.x-1...

As I said previously ( https://www.drupal.org/project/responsive_tables_filter/issues/3460918#c... 🐛 'tablesaw_type' is not a supported key. 'tablesaw_persist' is not a supported key. Needs work ), there is not yet a release for the 8.x-1.x version that includes the fix. I will work on that.

Release 8.x-1.19 is now tagged: https://www.drupal.org/project/responsive_tables_filter/releases/8.x-1.19 →

It includes the schema change present in the 8.x-1.x branch that resolves this issue.

The problem is that while the 2.x branch fixes this issue, it introduces a new one: https://www.drupal.org/project/responsive_tables_filter/issues/3460761 🐛 Module causes javascript problems in edit form Active .

Looks like that issue now includes a proposed code change that would resolve the issue. It would be wonderful if someone who is using this somewhat specialized setup (i.e., using this in conjunction with the Paragraphs module) could test that fix and report back. If that fix works, then people can still switch to the 2.x branch, rather than having to revert to the 8.x-1.19.

Thanks in advance for your help in moving this forward!

Thanks @mark_fullmer!

I'd be happy to test the solution for the other issue on the 2.x branch but I don't see any posts other than the initial issue description.

I don't see any posts other than the initial issue description.

Ah, my mistake then! I think I was confusing it with another issue I am following that is similar -- 🐛 Linkit field doesn't work in nested Paragraph when Auto populate link text is enabled Active .

Automatically closed - issue fixed for 2 weeks with no activity.