Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter pmheart6

    (@pmheart6)

    Ok, it appears to be a mobile chrome issue. (Desktop & mobile mode) … brave & Firefox also have the issue, but dolphin and Samsung’s built-in browsers work fine (the background of the plug-in is black instead of white on the working one)

    Plugin Author Phil

    (@philsbury)

    Hi @pmheart6,

    That error is normally when the REST API can’t be reached.

    In 3.0.6 a fallback was added to use Admin Ajax. Looking at it in Brave and Firefox, both are missing the Rest endpoint, but hitting the admin ajax version. I think the Rest one is because permalinks aren’t set. But both allow me access fine.

    That update was released early saturday so can you confirm this is still and issue?

    Thanks
    Phil

    Thread Starter pmheart6

    (@pmheart6)

    I noticed there was an update and I updated it before trying the other browsers when it still didn’t work that’s when I tried all the browsers

    Thread Starter pmheart6

    (@pmheart6)

    Setting a permalink on the ???? Page

    The front page? That’s the usual page that age-gate interrupts, but occasionally people may directly link to a page / post.

    So I should give each page a permalink? Or just redirect to the main page via a link on age-gate incase it fails?

    I dont know how to make sure it hits the rest api. I would think by now it’s enabled in most installations. I’m using hostmonster

    And yes, version 3.0.6 is installed

    Plugin Author Phil

    (@philsbury)

    Hi @pmheart6,

    You currently have “plain” permalinks (so ?page_id=123 etc), you just need to go into Settings -> Permalinks and pick whatever structure you want (/wp-admin/options-permalink.php).

    That should be all you need to do to have the api run

    I checked it on some android devices (all emulated, but would still expect errors) with firefox, chrome and opera and all worked. Unfortunately the test suit didn’t give me the default ones to try.

    Thanks
    Phil

    Thread Starter pmheart6

    (@pmheart6)

    Interesting doing the wp-admin it used a generic please leave and return [to main psge]. Age gate worked and took me logged in to main page.

    It’s not cashed (age gate toggle), and the other browsers weren’t tried till after updated to 3.0.6

    Is that because the css/ajax/rest is handled differently when going I’m via a logged in state. Redirect was not to wp-admin, but just the logged-in front page.

    Weird because if I was already logged in, I would have Been on Saturday too.

    • This reply was modified 3 years, 10 months ago by pmheart6.
    Plugin Author Phil

    (@philsbury)

    Hi @pmheart6,

    Just noticed that there’s a X-Endurance-Cache-Level header so it looks like there possibly is a caching plugin plugin in there. That could have cached stuff on Saturday on the server which could explain why is didn’t work then but does now (it has naturally cleared the cache). Seems the settings for that if it exists are under Settings -> General if you didn’t already know.

    But yes, normally being logged in you’d see an uncached version, but only if you were logged in in all the browsers, so a JavaScript file could have been and older version even after an update if that makes sense.

    Thanks
    Phil

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘[NSFW] An error occurred, please try again’ is closed to new replies.