Can’t enable cookie consent for google

Provided the details on your site contact page! Please check & let me know whats causing the issue!

@pixelyoursite I tried to contact with your staff from the contact form as this is kind of urgent no replies getting back to me. Can you please check the mail & let me know.

Thank you for your patience!

First of all, the cookie consent plugin you try to use (GDPR Cookie Consent by Webtoffee) overwrites our settings and blocks all tracking before consent is given. So even if we identify the specific problem you have with that button, it won’t have the desired effect.

Back to the initial issue, we can try to understand why it has this behavior on your website. But this makes sense only if you will use some other cookie consent plugin we integrate with.

So let me know what you decide before we proceed.

PS. No need to open multiple tickets with us, sometimes support can take time. Thank you for your understanding.

But as you can see GDPR Cookie Consent plugin is disabled right now. In that case we’re using no consent plugin but using Elementor to show cookie consent notice. In that case what to do? What’s the issue?

Right now all the tracking works.

Our plugin doesn’t detect Elementor cookie consent notice, so it will be ignored. As far as I can tell from your configuration, is just a normal pop-up.

I didn’t get you. I’m still not able to enable this option whenever I try to save it the option gets disabled again. Check the screenshot: https://prnt.sc/qxz54d
What did you mean by Elementor Cookie consent notice. It would work anyway without any plugin isn’t it? Can you please let me know what’s the problem & why it’s not working? I mean why it’s not getting enabled. As you’ve suggested I’ve disabled that plugin long ago so there’s nothing installed as cookie plugin. Please let me know what to do?

Here’s what I mean:

1. I don’t know why the button is not working, is something speciffic to your website.

2. That button will have NO EFFECT with a cookie consent popup from Elementor.

3. That button will have NO EFFECT with GDPR Cookie Consent by Webtoffee because they overwrite our settings and block scripts before consent.

4. At this moment tracking WORKS on your website.

Here’s what we have until now:

a. If you plan to use GDPR Cookie Consent by Webtoffee there’s no need to look into the button issue, because it doesn’t do anything.

b. If you plan to keep the Elementor popup, same thing, the error is meaningless.

What I’m trying to say, if you plan to keep the current settings (Elementor popup) or to return to GDPR Cookie Consent by Webtoffee, we don’t need to see what’s wrong with that button, because it doesn’t do anything.

Sorry if there’s any confusion!

@pixelyoursite While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.