Support » Plugin: Protected Posts Logout Button » button produces message but doesn’t log out

  • Hi just installed the plugin but it doesn’t seem to work.
    The text message does pop up.
    I have created this test page with a password of test . This is a password protected page.

    The same occurs on the “members only” page.

    Any help would be appreciated. Thanks very much.
    Glenn

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Nate Reist

    (@natereist)

    Hi @ve7gct,

    Sorry to hear you are having an issue with this plugin. I tested your page and I see what you mean. If you refresh the page you are now logged out, so the plugin is working but not forcing the page to reload. I tested this with google developer tools on and the refresh of the page then happens automatically. This leads me to believe plugin is working as it should, but the caching of the HTML from your server’s caching/expire headers is keeping the web browser from downloading a new, logged out, version of the page. Developer tools can disable the cache so the browser always must download the assets (html/images/css/js) on each request.

    Are you using a caching plugin or any .htaccess caching rules? If so, I would suggest disabling those and testing again to see if the issue is resolved.

    Thanks for your reply Nate. I am not using a caching plugin. Will try a couple of things including turning off various plugins to see if I can determine which one might be interfering. I will let you know what I find.
    Thanks again.
    Glenn

    Plugin Author Nate Reist

    (@natereist)

    I would think most likely this has to do with the servers’ expires and caching setting for HTML files.

    The server has an expires header on the response for the page to expire 1 hour in the future:

    Date: Mon, 04 Nov 2019 15:19:26 GMT
    Expires: Mon, 04 Nov 2019 16:19:26 GMT

    What that means is visitors will not get a new version of the HTML unless they do a hard refresh, or have caching disabled on their browser, like I said with developer tools.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.