🇳🇱Netherlands @thomasdik

Here is the patch:

ThomasDik → created an issue.

Apparently this is still an issue.
We used the module and the very moment we allow the marketing cookie and we get the iframe we have an iframe with a data-cookieblock-src attribute.

sjerdo → credited ThomasDik → .

This is already fixed.

Hi All,

Thanks for the help!
This kind of slipped through when updating multiple modules.
I've added the latest version of the patch and released it.

Kind regards,

Thomas Dik

Added fix for the mixup.

Kind regards,
Thomas Dik

ThomasDik → created an issue.

Ah turns out that the TYPE_HTML_RESTRICTOR needs a lot more to work properly; for a quickfix you can use TYPE_TRANSFORM_IRREVERSIBLE.

It should be the TYPE_HTML_RESTRICTOR as it restricts the iframe urls.

Not sure why this is still not fixed but here's a new patch.
There should be no untranslatable strings.
The nonbreakable space counts as html so it should be fine.

This is now fixed. I've taken the time to fix some codestyle issues and added a package file for compiling the javascript.

I had a look at the patch and it contains only the bare minimum.
There's been a change in the way we have to use once see https://www.drupal.org/project/drupal/issues/3183149 →

I will add the required changes :)

The changes are still in use in the V2.
I've updated the patch to match the latest version.

Updated the patch to match the latest changes.

Here's an updated version of the patch for the currently latest version 3.0.0-beta7

And another Re-roll agains the latest version 1.6.

I have merged the changes and updated the javascript to match the once changes in the core.

As the patch for the default value no longer applied for the default value I've updated the patch.

And the patch

ThomasDik → created an issue.

As the same logic persists in newer versions of the module I have created a new patch.
There are still no tests added.

As no one has answered this question.
This is due to a change in config.

You probably have this:

processor_configs:
  reset_facets:
    processor_id: reset_facets
    weights:
      build: '30'
    settings:
      link_text: 'Reset all filters'

Somewhere in your config files like facets_summary.facets_summary.[content_type]_facet_summary.yml
It should look like this:

processor_configs:
  reset_facets:
    processor_id: reset_facets
    weights:
      build: '30'
    settings:
      link_text: 'Reset all filters'
      position: null

And the position can be either null/before/after/replace please have a look at the ResetFacetsProcessor for details.
But this should fix your issue.

Kind regards,

Thomas Dik