Muhammad

Hi @rvof,

Thank you for sharing these code suggestions.

We’ll check with our development team to see if these changes can be applied, and we’ll let you know once we have an update.

If the issue is persisting on your setup, please feel free to reach out to us via email at support(at)wpfolio.com so we can assist you directly, including providing a temporary downgrade if needed.

Thanks for your patience and for helping us improve the plugin.

Hi @rvof,

Thank you for reporting this issue!

The warning “Undefined array key ‘anylc_nonce’” may be related to our new opt-in usage tracking feature. It appears when the usage-tracking request doesn’t receive the expected nonce value in the admin area. This is only a PHP notice and shouldn’t break your site, but we certainly want to clean it up.

To help us pinpoint the trigger, could you let us know what action you were performing when the message appeared (for example, dismissing the opt-in prompt or saving settings)?

We appreciate you bringing this to our attention

Hi @eagles051387,

Thank you for reaching out!

The developer tools alert is meant to prevent unauthorized access, but if it’s triggering randomly, that’s not expected.

As a temporary fix, you can disable the alert by adding this to your theme’s functions.php or a custom plugin:

add_filter('pda_disable_developer_tools', '__return_false');

Could you also share your device, browser, and PDA plugin version? This will help us investigate further. Feel free to reach out via our contact form with details.

We appreciate your patience!

Hi @rycreat10,

Thank you so much for taking the time to share this wonderful review! 🌟

We’re truly grateful for your kind words and thrilled to hear that you’ve had such a positive experience with both our support team and our plugins. The WP Folio team really appreciates the shoutout, it means a lot to us!

Your satisfaction is always our top priority, and knowing that our efforts made a difference genuinely motivates us to keep delivering the best service and products we can.

Thank you again for your trust and support! ❤️ If you ever need anything else, we’re always here to help.

Hi @compassionateveg,

Thank you for sharing your thoughts, we appreciate you giving PPWP a try.

Just to clarify, our free version does allow you to lock the entire site behind a single password. Many users find this meets their needs for basic sitewide protection.

Excluding only certain pages such as keeping the homepage public while the rest of the site is protected, requires more advanced rules and is part of our Pro features. That’s why the upgrade is needed for this specific setup.

We understand that every site has different requirements, and your feedback helps us continue improving the plugin and our feature offerings. If you’d like to share any additional suggestions, we’re always happy to listen through our official support channels.

Thank you again for your review and for trying out PPWP.

Hi @adam7hansen,

Thanks for reaching out.
 
Regarding the issue you’re seeing with the [ppwp] shortcode showing “Empty content, invalid attributes or values” in red, could you please double-check if you’ve enabled the “Use Shortcode within Page Builder” option?
 
You can find it by going to:
Password Protect WordPress > Partial Protection > General in your WordPress admin dashboard.
 
Enabling this option usually resolves shortcode rendering issues within page builders.
 
Let us know if it works.

Hi @mica123,

Thanks for reaching out, and I’m glad to hear PPWP Lite has been working well for you.

To disable the Sitewide protection, please go to:

WP Admin → Password Protect WordPress → Sitewide Protection tab

You should see the Sitewide Protection section there. Simply toggle off the “Password Protect the entire site” option and save your changes. Once disabled, the site will become publicly accessible without needing a password.

Regarding your second question:
If you deactivate the plugin, the password protection will be removed immediately. When you reactivate PPWP Lite, the previous settings—including the global password—will remain exactly as before unless you manually change or remove them.

If you still don’t see the global password field or the settings page, feel free to share a screenshot and we’ll help you check what might be happening.

Let me know if you need anything else!

Hi @sadhaka,

Thanks for bringing this to our attention.

The notice you’re seeing

“Passing null to parameter #1 ($string) of type string is deprecated”

usually appears on sites running PHP 8.1 or higher. It doesn’t affect your site’s functionality, but we’ll pass this along to our development team to review and ensure full compatibility with the latest PHP versions.

In the meantime, you can suppress such notices by setting WP_DEBUG_DISPLAY to false in your wp-config.php file if needed.

Appreciate your patience and for helping us improve the plugin!