jackgoff222

Hey,

Thanks for getting back! It would seem suggestion 2 was the one that worked for me; everything is going as intended and has been for several hours without the issue reoccuring.

Thank you so much! That had been driving me insane!

Hey again,

I’m still getting the issues present but my host at WP-Engine is attempting to help. I’ve attached her response because she asked me to reach out and see if you had any recommendations.

“I sincerely apologize for the delay in getting back to you. I’ve been thoroughly testing different configurations to resolve the Age Gate issue. Here’s a summary of everything I’ve tried:

• Tested various settings within Age Gate, including enabling the local storage option.
• Excluded all Age Gate-related assets from optimization to prevent conflicts.
• Adjusted multiple settings within PSB to find a configuration that works. 
• Tested NGINX rules and web rules to set cookies and create cache variations based on user groups.
• Tried using a dynamic content cookie approach to ensure users don’t get repeatedly challenged.

Despite these efforts, the issue persists. To be honest, I’ve run out of ideas on how to troubleshoot this further. I also reviewed the plugin’s documentation, but they don’t provide many details on exactly how the validation works and how it is stored, making it quite challenging to pinpoint the root cause.

Would you be able to reach out to the plugin’s developers to see if it’s possible to set a cookie for:

1. Pages where users haven’t passed the challenge.
2. Pages where users have passed the challenge.
3. Pages where users failed the challenge.

If this were possible, we could attempt a dynamic content approach based on cookies again. Currently, when a user hasn’t passed the challenge, no cookie is set—then, upon validation, the cookie changes to age-gate=1. I tried manually setting age-gate=0 for users who haven’t passed yet, but once they do, the cookie does not update to age-gate=1, so I assume I’m missing something around the validation logic.

It would be helpful to get their input on whether there’s a better way to handle this via cookies, or if they have another recommendation.”

If you have any suggestions I’d appreciate them – I’m currently running my site without any optimizations due to this issue. Thanks

Hey again

I’ve used the troubleshoot mode, switched user to a customer and even turned off my account, removed cookies so I could see the age gate window which appeared correctly but the error couldn’t be replicated. I assume because Nitropack wasn’t caching these troubleshooting pages.

Anyway, with Nitropack disabled everything works as intended on the main site, the issue does not appear but I still don’t understand how I can prevent it from causing issues. there is a section for

“Shortcodes exclusions

Load widgets, feeds, and any shortcode with AJAX to bypass the cache and always show the latest content.”

If that’s any help to bypass anything? I’ve already Age Gate to be excluded from their Javascript minify too using all the js scripts I found.

Hey there,

Thanks for getting back in touch. I can’t seem to find a place to whitelist cookies in “Complianz” – the cookie banner I’m using. But the issue isn’t that I believe.

Once you’ve accepted cookies, if you refresh the page by reentering the link, or clicking the logo (not by pressing F5 weirdly), Age gate will reappear.

The css animation also isn’t playing but, that will play just fine if I purge Nitropacks cache and use the website within the first 10 minutes, before it, seemingly, caches Age Gate. It’s also set that if you press No it’ll take you back to google, this works fine unless it’s been cached – Pressing No will just close Age Gate as if you accepted the cookies. No idea what’s going on.