“Script blocking” feature and inline scripts

We had your “script blocking” feature enabled and it was breaking our checkout, because it was disabling inline scripts (added to existing enqueued scripts) until consent was provided. This is REALLY bad and not the expected behaviour.

It’s super questionable to me whether a consent plugin should even affect scripts at all. But since you want to provide this “feature”, it should be clearly and explicitly stated on the plugin page whether this is the default or not (I sure hope it isn’t!) and that it REQUIRES testing after enabling such a feature.

The “script blocking” list only lists a few plugins and gives the option to enable/disable scripts for those. There is no option on that page or on the plugin settings at all that even mentions inline scripts and gives you the option to not disable them. Fortunately the entire feature could be turned off on that page (but not in the settings?)

I suggest you add some settings to the Advanced tab belo the Advanced Script Rendering option… One for script blocking and a separate one for inline script blocking – defaulted to OFF so that activating your plugin doesn’t break any necessary scripts.

Oh and some extra notes on the plugin page and in the documentation about this somewhere, as I couldn’t find anything and it took me an hour of searching around to work out it was your plugin and where to turn this off, after another hour of trying to work out why the checkout didn’t work for new site visitors. And I’m a dev myself, lucky to find this during routine testing. I can’t imagine what other users would do – just not realize things are even broken I guess!

• This topic was modified 1 year, 3 months ago by Tony Hayes.