• Resolved vieckowski

    (@vieckowski)


    Hello,

    By default, clicking the “Accept” button on the consent bar reloads the page with all consents accepted/enabled. So reloading is the way to get them enabled. This reloading is not the best UX solution and as far as I’m concerned, most services, wether it’s small blog or big, multimillion ecommerce sites don’t require the page to reload.

    Is there a way to make this plugin to work in a way that doesn’t require the page to reload and have all consents enabled by default?

    I understand that GDPR forces me, a website administrator to give user a clear information and a choice to decide which consents he wish to approve, but it seams today, that these legal requirements can be met, even when the consents are enabled by default and You give the user a clear information to accept these conditions or to change the settings to disable it.

    Or I’m wrong, and all these services without page reloading use solution that is able to enable, accept all consents without page reload?

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • We’re reloading the page to make sure the consents are added correctly. I don’t understand why that would be a problem with the UX. I think users understand that something happens when they press on the ‘Accept’ button.

    You can add consents that are ‘required’. This means it will be loaded by default, no matter the users preferences. Keep the GDPR compliance in mind when doing this.

    Thread Starter vieckowski

    (@vieckowski)

    Hi,

    Thank You very much for fast response as well as for all Your approach for WordPress community delivering such nice, free plugin.

    However, I’d argue that page loading isn’t a real issue. What user understands and what he doesn’t is one thing, but page loading time in general (or loading the page twice) is a statistical issue, and every second of page load increase user abandonment probability. That’s a fact. Plus, I’d say that loading the page twice to experience it, is a user experience issue.

    As I mentioned I don’t meet any of really big (or most of smaller, regular websites) web services reloading the page after user accepts consent – and we have no doubt that they have a pretty good GDPR/lawyers support.

    This is also how other, paid/not free, WordPress GDPR plugins work – the consents are by default disabled, but accepting the consent by a user doesn’t make the page reload.

    Anyways, You’re doing a great job !!!
    Best, Simon.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘No page reload after “Accept “’ is closed to new replies.