Phil

You can prevent the cookie from being set to get this behaviour:

add_filter('age_gate/cookie/set', '__return_false');

Thanks

I can see what is happening, but not why.

it looks like there’s a ln error happening just before the end of the document, so the JavaScript isn’t loading at all causing the slider and age gate to not render. If you have access to the logs it should hint as to why.

I’m away the next few day but can look to fix early next week if there’s something obvious in the logs

thanks

Phil

Hi @budzdeli and @denniepasman – this has now been resolved in v3.6.2.

Thanks
Phil

Hi @devbydech,

It’s a setting: Age Gate -> Messages -> Aria label

Thanks
Phil

Hi @jackgoff222,

I’m honestly not sure what they are talking about!

They’ve also confirmed it’s because Age-gate is unable to access Local Storage

Why would this be the case? Unless they are nuking local storage entirely (which doesn’t seem to be happening as I see elementor has access to it and I’d assume Woocommerce does too)

it wouldn’t work with the PSB either way

Not sure why this would be either as there’s nothing that is preventing the cookie being set – and in fact, read. I’m am as confident as I can be that reading and setting the cookie is not the problem;

Looking at the staging site has given some clues though. Let me walk through what I’m seeing:

• I visit the site, no cookie is set
  • Age Gate shows and the HTML has the classes age-gate__restricted age-gate__restricted--js appended. This happens when we check for the cookie and it doesn’t exist. So, so far things are as expected.
  • However, inspecting the code, the <template> tag that stores the Age Gate pop up is empty. This is not what I would expect
  • If I run age_gate_hide() in the console, Age Gate is hidden
  • But if I then run age_gate_show() in the console, it doesn’t return and I’m greeted with and load of errors (errors are expected without the markup)
• So now I refresh, and click “Yes”.
  • I can see the cookie is now set
  • On refresh, the cookie is still set and – critically – age-gate__restricted age-gate__restricted--js are not present on the HTML element. This is because Age Gate has successfully read the cookie and has determined we don’t need to show the Age Gate.
  • But the form is still present, why?

So for the last point, the empty template tag for age gate is probably the tell. Looking at how nitropack adds things to the page it looks like everything is being wrapped in a template tag which is later added to the DOM. This seems to happen all the time so is probably in their tools that construct the final HTML output.

Ways to resolve the issue I think are:

1. Nitro pack does not empty template indiscriminately into the HTML or;
2. In the Age Gate Advanced settings you could change the Template render element to ‘script element’ and see if that works or;
3. There’s a way to omit the Age Gate template from their output which might be possible with the nitro-exclude attribute.

For the last option there, I’ve updated the dev build on the same url as before and you can add the following to your functions.php:

add_action('init', function(){
    age_gate_add_attribute('age-gate-template', 'nitro-exclude', '');
});

Hopefully one of those ways will solve it. Like I say, I am confident cookies are not the issue and the support team there are giving you the wrong info.

If you have any issues going forward it might be best to reach out via the website as I’ll probably be able to give more in-depth options that way if needed.

Thanks
Phil

Hi @mciac,

There’s no a built in way to do this, but there’s a guide to doing just that in the documentation here.

Thanks
Phil

Thanks @kimecho,

I think there’s maybe a server issue, not internal xhr requests are resolving for me on Safari (desktop and mobile) which is why things aren’t working as expected

In the above, the ones in black are external, the last two in red are age gate, schema and refill are CF7. Are you also having issues with contact forms.

Why this would only be in safari I’m not sure.

I also noticed this code:

document.addEventListener("click", function (event) {
    let button = event.target.closest(".age-gate-accept"); // Target the button
    let ageGateWrapper = document.querySelector(".age-gate__wrapper"); // Target the popup wrapper

    if (button && ageGateWrapper) {
        console.log("Age gate accepted - hiding popup");
        ageGateWrapper.style.display = "none"; // Hide the popup
    }
});

Is this a workaround for the above?

If you’re up against it time wise, then you could use that code to also set a cookie:

document.addEventListener("click", function (event) {
    let button = event.target.closest(".age-gate-accept"); // Target the button
    let ageGateWrapper = document.querySelector(".age-gate__wrapper"); // Target the popup wrapper
    
    if (button && ageGateWrapper) {
        console.log("Age gate accepted - hiding popup");
        ageGateWrapper.style.display = "none"; // Hide the popup
        expires = "; expires=" + 0;
        document.cookie = 'age_gate' + "=" + 18 + expires + "; path=/";
    }
});

Far from ideal, and I’d see if you can find why the calls are being rejected in safari on cloudways if you can

Thanks
Phil

Hi @kimecho,

If you’re able to activate it on your site I can have a look. Perhaps do it on Friday if today isn’t possible and I’ll be able to have a look over the weekend.

Thanks
Phil