• hey there,
    we’re getting a blank page now, here’s the console error (i’ve removed the url & replaced with … for privacy).

    Uncaught Error: Your focus-trap must have at least one container with at least one tabbable node in it at all times
    	w .../wp-content/plugins/age-gate/public/js/age-gate-public.js?ver=2.19.0:5
    	activate .../wp-content/plugins/age-gate/public/js/age-gate-public.js?ver=2.19.0:5
    	value .../wp-content/plugins/age-gate/public/js/age-gate-public.js?ver=2.19.0:1
    	value .../wp-content/plugins/age-gate/public/js/age-gate-public.js?ver=2.19.0:1
    	value .../wp-content/plugins/age-gate/public/js/age-gate-public.js?ver=2.19.0:1
    	e .../wp-content/plugins/age-gate/public/js/age-gate-public.js?ver=2.19.0:1
    	<anonymous> .../wp-content/plugins/age-gate/public/js/age-gate-public.js?ver=2.19.0:1
    	jQuery 2
    age-gate-public.js:5:2824

    any ideas? this site is hosted on cloudways, no css or js minification is enabled.
    thanks,
    Json

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Phil

    (@philsbury)

    Hi @minion08,

    I can’t reproduce this, but I’ll keep looking. I’d suggest turning off the focus trap in Age Gate -> Advanced settings and seeing if that fixes things.

    Thanks
    Phil

    Thread Starter Json Koning

    (@minion08)

    thanks Phil, I deactivated Breeze completely (Cloudways caching plugin) & the issue disappeared. I only had the bare minimum enabled in Breeze, so I’ll see if I can work through it, as I’d prefer to have some kind of caching enabled.
    I’ll report back.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘No longer working – uncaught error’ is closed to new replies.