Complianz and firefox

  • Resolved alex72b

    (@alex72b)


    2 years ago

    Hello I have a problem with complianz and firefox. On my page are scripts from fupa included. If the page is loaded the first time after the visitor agrees, everything is fine. If the page is loaded a second time, then the scripts are not called correctly. The problem only occurs with firefox. With Chrome everything is fine. Do you have a solution?

    To explain: The page is a test page, on which I always test updates first, before I put them on the main page. The main site is still running with version 5.5.2, the test site with version 6.3.5.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @alex72b If I put behind the url ?ao_noptimize=1, the scripts seem to run on reload. Can you check if this is the case?

    If so, you can maybe exclude some scripts from autoptimize to tweak your setup.

    Thread Starter alex72b

    (@alex72b)

    I tried your tip and I disabled the plugin “autoptimize”. Unfortunately it did not work. Do you have another idea?

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @alex72b,

    I also see WP Fastest Cache, so could you test the behavior of the script without that plugin enabled as well?

    Kind regards,
    Jarno

    Thread Starter alex72b

    (@alex72b)

    Thank you for your quick answers.

    I disabled WP Fastest Cache. But it didn’t change.
    What can I do next?

    Best regards
    Alex

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @alex72b,

    Strange one, as I see a console error relating to Elementor; which only appears in Firefox and only after a reload, like you said.

    When a blocked script doesn’t behave correctly after consent, there is an alternative approach that you can try instead.

    Instead of blocking the script from within the Script Center (Complianz > Integrations > Script Center > Block a script, iframe, plugin), what you could try instead is to wrap these embeds between consent area shortcodes:

    [cmplz-consent-area category="marketing"]
Your embedded content
[/cmplz-consent-area]

    Further details about this approach and some CSS to style the notice are provided here: https://complianz.io/wrapping-content-in-consent-shortcodes/

    Could you check if that method causes these embeds to respond as intended in Firefox?

    Kind regards,
    Jarno

    Kind regards,
    Jarno

    Thread Starter alex72b

    (@alex72b)

    Hello,

    Thank you for your message. I did some more testing because of your info and found that the problem is related to the third party script and Elementor. I did a test installation locally without Complianz, on which the error also occurs. The fact that with Complianz version 5.5.2 the error was not visible seems to be because Complianz 5.5.2 solved the problem (but i don’t know how) and did not cause it.

    Best regards
    Alex

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Complianz and firefox’ is closed to new replies.