Support » Plugin: Complianz - GDPR/CCPA Cookie Consent » Manage consent button still does not work after 4.9.4 update

  • Resolved mistergeko

    (@mistergeko)


    Hi Complianz Support,

    I have read this thread the other day: https://wordpress.org/support/topic/manage-consent-button-doesnt-change-anything/ and followed to see will this new fix change manage consent button behavior, but it still does not do anything for my website. It keeps just reloading the page and again status is “accepted”, while before few updates it worked normally.

    I cleared the cache, reconfigured everything within Complianz again, cleared cookies in the browser, tried different browsers, still the same issue.

    Hope you can take a look into it again.

    Thanks in advance,
    Geko

    • This topic was modified 3 months, 1 week ago by mistergeko.

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

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author RogierLankhorst

    (@rogierlankhorst)

    Hi @mistergeko,

    You’re right, we incorrectly treated this issue as part of another fix.
    I’ve created a fix here:
    https://github.com/Really-Simple-Plugins/complianz-gdpr

    We’ll have to run some additional tests to see if this fix doesn’t interfere with the opt-out or categories banner and other possible combinations of regions and banner setup, then release it.

    If you can confirm this fix is working for you that would be great!

    Thread Starter mistergeko

    (@mistergeko)

    Hi @rogierlankhorst,

    I have intalled the fix and tested it now and I can confirm it’s working great!

    The other tests whether everything else is okay with the plugin, I leave that to Complianz team 😀 to me nothing seems broken from what I could observe.

    Thanks a lot for the fix, highly appreciated. I realized I did not leave a review yet, so you have absolute 5 stars from me. Such a great plugin, such a great support team!

    Kind regards,
    Geko

    Plugin Author RogierLankhorst

    (@rogierlankhorst)

    Great, thanks for confirming!

    Hi @rogierlankhorst @mistergeko

    Came here after installing the update, and this thread linked to the initial issue I raised too! Confirmed that the “official” update released didn’t fix the issue for me, but I see the “unofficial” release on GitHub resolves it…

    @rogierlankhorst – if I install the version on GitHub you’ve shared, then when you officially release the next update, would there be any conflict with me updating it (e.g. if there are additional minor changes in your new official release)? Sorry if that’s a complete novice question, but I’ve not installed unofficial updates in WP yet!

    Thank you,
    Becky

    Thread Starter mistergeko

    (@mistergeko)

    I think when the plugin releases official new version it will override everything in the plugin directory, that’s how WP works, but let’s also wait for the official confirmation from the plugin authors 😀

    Plugin Author RogierLankhorst

    (@rogierlankhorst)

    Hi @beckyrbsn, @beckyrbsn,

    Yes, when the update is released through WordPress, it will just override the one from Github. You might need to reactivate the plugin after the update.

    Sorry for the delay in fixing this. Official release should be somewhere next week. We want to test all possible combinations to make sure it’s working as it should now.

    Thank you – will await for the official release since you will be doing the testing. Let me know if I can help with your testing though.

    Thread Starter mistergeko

    (@mistergeko)

    The update 4.9.5 update broke the fix you have sent me from github. Seems the problem is back again. I’m going to roll back to that fix again. Just letting you know.

    Plugin Author RogierLankhorst

    (@rogierlankhorst)

    Thanks for reporting @mistergeko,

    This is because the branch with the fix for this issue wasn’t merged yet: the test team wasn’t ready with testing on this branch.

    We’re aiming for next week.

    Thread Starter mistergeko

    (@mistergeko)

    Oh thanks for letting me know that. I thought maybe it was again some other issue 😀

    Anyways, I’m gonna wait until I see that fix in the changelog then.

    Thnx

    beckyrbsn

    (@beckyrbsn)

    Came back here again because I noticed the same as @mistergeko. Thanks, will wait for the new update.

Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.