Muhammad

Hi @938htisn,

Thank you for reaching out!

Yes, you can definitely add a logout button to let users exit the password-protected area. Please use the following shortcode:

[ppwp-logout]

This will display a “Log Out” button that clears the password cookies stored in the user’s browser.

Our plugin also supports additional attributes (like type, post_ids, label, id, class, etc.) if you want more control over which cookies to remove or how the button looks. You can find the full list of available attributes in our documentation.

Hope that helps!

Hi @ccalifano,

Thanks for testing and sharing the details. Since you’re on Pro, another option worth trying is our Section Protection feature. It lets you protect specific blocks or sections directly from the editor, which avoids potential issues with custom templates not processing shortcodes.

Here’s our documentation on how to set it up:
https://passwordprotectwp.com/docs/section-protection/

Could you please try protecting your content this way and see if it works as expected? If the issue persists, kindly reach out to us via our contact form with the information below:

Some screenshots of:

• Your Edit page screen 
• PCP Passwords tab

Hi @ccalifano,

Thanks for the detailed info and test page.

It looks like you’re trying to use a PCP Global password with the shortcode (pwd="23"). Please note that this feature is only available in our PPWP Pro version. If you’re using the Lite (free) version, that would explain why the password isn’t being recognized.

In PPWP Lite, you can protect content sections with the shortcode below instead:

[ppwp passwords="password1 password2"]Your content[/ppwp]

Here’s our documentation for your reference:
👉 https://passwordprotectwp.com/docs/password-protect-wordpress-content-sections/

If you are already on PPWP Pro, then the issue may be related to your custom “blank page” template or a conflict with another plugin/theme. In that case, I’d recommend temporarily switching to a default theme and disabling other plugins (except PPWP Lite/Pro) to see if the shortcode works correctly.

Could you also confirm whether you’re on the Lite or Pro version? That will help us guide you more precisely.

Hi @ccalifano,

Thanks for reaching out and for sharing the details you’ve already tried. A couple of quick checks so we can narrow this down:

1. Could you confirm the exact shortcode you’re using on the page? (e.g. [ppwp pwd="16"]Your protected content here[/ppwp])
2. To help us reproduce the issue, would you be able to create a temporary test page with a dummy password (not tied to sensitive content) and share the link here? This way we can see the behavior directly.
3. Just to confirm, are you testing with the Global Password feature or a (PCP) password?
4. If possible, please try temporarily deactivating all other plugins except PPWP Lite and PPWP Pro (if you’re using the Pro version). This will help us check if a plugin conflict might be causing the issue.

Once we have that information, we’ll be able to guide you further.

Looking forward to your update!

Hi @divaldo100,

Thanks for providing the test page and password, I tested it on my side and also noticed the delay.

The slowdown may be related to the large number of passwords being processed on the page. Each password is checked individually, so the more passwords stored, the longer the login process can take. This is especially noticeable when you have 30+ passwords.

Here are a few steps we can take to improve the speed:

1. Reduce the number of stored passwords where possible — removing older or unused ones can help improve performance.
2. Consider using a single “Master Password” (if your use case allows) instead of many separate ones, this will greatly reduce the number of checks needed.
3. Check for plugin/theme conflicts: your debug log shows some notices from other plugins (“custom-facebook-feed”, “google-calendar-events”) and the theme (“bard”). Disabling these temporarily or switching to a default theme can help confirm if they’re adding extra load time.
4. Enable object caching or a performance plugin: this can help reduce repeated database lookups for password checks.

Let me know if that helps.

Hi @silvalau,

Thanks for sharing the detailed findings and the sample page, I tested it with the provided password, and it worked fine on my side as well.

It’s great that you were able to identify the ad injection conflict. I’ll share your questions and the Markdown script with our development team so they can review how PPWP processes content inside its wrapper and advise on safe ways to inject ads without interfering with the password form or reCAPTCHA.

Once I have their feedback, I’ll update you here.

Thanks again for your thorough troubleshooting and for providing a working example, it’s very helpful.

Hi @adamjay123 ,

Thanks for getting in touch!

This issue where WPBakery Tabs display as plain text until the page is refreshed, usually indicates that the tab layout JavaScript isn’t being properly triggered after the password is submitted. Since this only happens on password-protected pages, it’s likely related to how the content loads after authentication.

To help narrow things down, could you please try the following:

1. Temporarily deactivate all other plugins except PPWP Lite and PPWP Pro (if you’re using the Pro version). This will help rule out any conflicts with other plugins.
2. Switch to a default theme like Twenty Twenty-One to test whether the issue might be theme-related.

Once you’ve tested with only the PPWP plugin active and a default theme, please check if the issue persists. If it works fine under those conditions, we can help you pinpoint the conflicting plugin or theme.

Looking forward to your update!