Nate Reist

Hi Agnes,

I’d love to try to help you out. Couple things come to mind. The sidebar needs to render shortcodes, not all widgets do that. Can you send a sample URL where you are experiencing this issue?

-Nate

No problem, I pushed 1.4.3 just now with this patch applied. Let me know if this works.

Thanks @rcreactors, @gahapati, and @gserafini

• This reply was modified 5 years, 11 months ago by Nate Reist.

@fogwny Yes, that is possible to include in the text widget using the shortcode: [logout_btn], as long as the widget supports shortcodes, which by default it should.

You can disable it being added to the content on the settings page by setting the option for Automatically add button to protected pages to “No”

Hope this helps.

-Nate

Unfortunately, there is no multi-language support with this button. It would require an update to the features of this plugin. Are you using the shortcode or the template tag to place the button the page, or just relying on the default filter?

It could either be a JavaScript error or an error not allowing non logged in users access to the wp-ajax.php for the logout script to complete logging out. There could be many factors causing that, like security plugins or measures blocking wp-admin access, other plugin conflicts, or javascript errors in general.

I see no logout button on your example page, so it would seem this plugin isn’t active anymore unless you it is not set to show up with the content filter? or are you using the shortcode or template tag?

Those are internal WordPress programming tools.

The heartbeat API is a tool that can check at a regular interval with the server and get data over a XMLHttpRequest using JavaScript. It runs like a clock tick,
for example: every X seconds, check for new posts..
The AJAX API is similar, Javascript makes a XMLHttpRequest to the server but you usually would do this when some action happens from a user, for example: when a user completes form submission or clicks a button.

Both of those happen in the user’s browser (chrome, safari, firefox etc.) on their computer and then talk to your web host (server) which must be listening for that XMLHttpRequest. The server can then process that request, and return a response that can be used to accomplish something in your user’s browser without out them reloading the page or in your case, it could force the browser to reload if the cookie had expired.

That would require custom code to implement, I don’t know of any plugins available that would allow you to do this without writing some custom code.

2. No idea, how/where would I find this out?

This codex page shows how you could check for Javascript errors.

3. Do you have any caching or minify plugins installed?

I could probably tell you from a list if you had any caching or minifying plugins.

4. If my answers to the above are helpful, I could try that out.

If you create a sample page that is password protected and supply the link to that here as well as the page password I can look at the page and see if there are any apparent issues.

Please do not send your wordpress password publicly, only the sample page password.

Hey @rloveday,

Sorry you are experiencing some issues with the cookie time. Unfortunately that is expected behavior in the instance you have explained. Hitting the back button doesn’t re-render the page with PHP ( which is where the cookie check happens ), but just steps back a step in the browser history, to a point where you were already logged in, it doesn’t check at that point, that is why a page refresh is required to log you out of password protected posts and pages.

In order to get the page to automatically log you out without a page refresh, would need to have a process that checked on the server whether the password cookie had expired, then if it had, that process would need to refresh the page for you automatically. This could be done with a Javascript using the WP heartbeat api, or an interval function using WP AJAX. In either process you would need to have an action listening on the server ( PHP ) to return to you whether or not it had expired.

@techwizardsupport I think instead you would need to use remove_filter, not remove_action, to remove it from the content. Then you may want to set up a function that calls that function pplb_logout_button, so you can wrap it in HTML to make it display nicely.

Hey @blath,

I’m afraid I don’t know what you are referring to?

thanks

Hey @rloveday,

Sorry to hear you’re having issues. Can you answer a few questions for me that might help me give you some advice?

• What theme are you using?
• Are there any javascript errors in your browser’s console/developer tools?
• Do you have any caching or minify plugins installed?
• Can you share a link to the page a sample protected page and password that I can inspect/debug? Please note, do not share anything sensitive that could compromise the security of your website or content. You can create a simple test page and give it a non-important password.

• This reply was modified 8 years, 5 months ago by Nate Reist. Reason: html fix

Hi spanizhfly,

Sorry to hear you are having issues. Is the plugin not logging you out of wordpress? or out of the protected page? The 300 second value would just make that logged in cookie expire in 5 minutes.

@gahapati, I will try to make that revision soon for a new release.

Thanks for your patience.

Hey Tim,

Sorry about that! I patched the plugin to include that function again and made it just call the shortcode, so that it doesn’t need to create a new instance of that class. Thanks for the heads up!

Nate

It should work for both.