Password Protect WordPress Page Support

Hi @kristelc,

Thanks for reaching out to us last night.

You’re trying to translate our password form on a second language, aren’ you?
If so, which translation plugin are you using?

Our PPWP plugin supports the top WordPress multilingual plugins including WPML.

Otherwise, to assist you better, may we know why you want to use different password forms on different pages?

Hi @opensesamebuns,

Thanks for reaching out to us.

We actually password protect WordPress the_content hook. So by default, the excerpt is protected as well. We will develop a new feature that allows showing the post excerpt even if it’s password protected in our upcoming version.

The featured image is not a part of the_content though. So it’s actually not protected and should show up on your blog post.

It could a theme display issue. You may want to double-check your theme setup or drop us an email to hello(at)preventdirectaccess.com with some sample URLs and screenshots so that we can take a look at it for you.

Hi @sisdev,

Have you had time to read our thoughts on the issue yet?

Can you please follow up and allow us to help, please @sisdev?

Elena.

You’re brilliant! Thanks, @rinkul123.

Yes, Open Graph becomes a standard way to control how your page is shared on social media such as Facebook and Whatsapp.

I’m just not sure if users really want to protect the Open Graph meta tags, together with the content as well.

In fact, many users would like their private content to be protected while still showing the page excerpt or meta description tags to entice their readers to join their membership site or buy certain products.

May I know why you would like to protect your page preview on social media?

Anyway, we’ve created a feature request here for you – Password Protect Open Graph Meta (Description) tags.

If there is enough user demand for this, we will definitely consider supporting it in our upcoming version of PPWP.

Hi @rinkul123,

Thank you for reaching out to us last night.

Our team has done a quick test. And we can’t reproduce your reported issue on our side.

Technical-wise, we also confirm that there is almost no way the content of a password protected page could be showed on Facebook or Whatsapp unless it’s cached, which is likely to be the case here.

For example, if your page is already shared on Facebook or Whatsapp before protection, the page preview including its featured images and excerpt is cached.

Once you password protect your page with our plugin, the content is now locked but still cached by those platforms. As a result, it will still display on Facebook and Whatsapp.

What you can do is to clear the cached content using tools like Facebook Sharing Debugger after protection.
https://developers.facebook.com/tools/debug/

Please let us know if it works and makes sense to you.

Elena

PS. You may want to drop us an email to hello(at)preventdirectaccess.com for better and faster support on this issue.

Hi @sisdev,

Thank you for the follow-up and explanation. We really appreciate it.

Our team has just done quick testing with WPBakery. And both our entire page and part of content protection are working correctly.

It could be something to do with the server cache or configurations. Some servers may return cookies differently than the standard.

Do you mind sharing with us a sample password protected page so that we can take a look at the issue?
That would help us figure out what goes wrong fairly quickly.

We look forward to helping you get it resolved quickly, @sisdev.
Elena.

Hi @sisdev,

Thanks for reaching out to us.

Can you please let us know which protection method you’re using first, please?

There are quite a lot of reasons why your passwords are not accepted on the front-end. For example:

• You’re using a Custom Page Template
• You’re protecting content on a custom field
• You’re using an unsupported caching plugin or server and many more

Can you please let us know so that we can help you accordingly, please @sisdev?

Hello @janalkelly,

Thanks for reaching out to us last night.

In order to assist you better, do you mind letting us know a sample page URL that iPhone users have to enter password twice to access the content?

P.S. You may want to drop us an email to hello(at)preventdirectaccess.com so that we can reply to you much quicker and easier.

Hi @robword,

I’m so sorry to hear that you’re running into problems with our plugin.

It looks like an htaccess conflict.

Have you managed to resolve the issue yet, Rob?

Do you mind dropping us an email to hello(@)preventdirectaccess.com so that we can help you better & faster?

Hi @zmorse,

Yes, it’s possible to know which users who log in to your password protected pages with our Pro version and Statistics add-on.

You will be able to know the exact time they enter the password, together with their username(if available), browser and IP address.

Hope it helps ??

To summarize, the issue happens because of the user’s server configuration whose referrer policy is set to “no-referrer”.

It should be set to “no-referrer-when-downgrade”, which is secure enough, and at the same time, improve compatibility with other plugins like ours.

The issue is resolved via email.

We’ve officially dropped support for WordPress version 4.6 and below and updated our readme accordingly.

Hi @khodiak,

Thanks for letting us know.

It looks like a conflict with an old version of WordPress. Our team is checking on this.

Would you mind dropping us an email to hello(at)preventdirectaccess.com so that we can update & follow up with you faster?

Hello @kelsey04108,

Thanks for reaching out to us with a very clear explanation.

Based on your provided information, it looks like:

• Our plugin is still working as when you click on the back button, the protected page content displays correctly.
• There is a conflict with your existing theme or plugin, which automatically redirects users after they enter the correct password.

Can you please drop us an email to hello(at)preventdirectaccess.com so that we can assist you faster and better?

We look forward to your reply, @kelsey04108

Hello @pwsean,

This is our last and final request. Hope it doesn’t sound annoying to you.

Would you be kind and caring enough to check and revise your review as promised, please @pwsean?

It will be unfair and extremely demoralizing for us, a new and fast-growing plugin, to get a 1-star review from a hasty decision as what you’ve admitted.

Hope you’ll consider our request.

Anyway, happy Friday and the upcoming weekend ??

Elena
The PPWP Team