Muhammad
Forum Replies Created
-
Forum: Reviews
In reply to: [Prevent Direct Access - Protect WordPress Files] Great protectionHi @wildvanvorm,
Thank you for your message.
We’ve already replied to you by email and are reviewing your subscription details.
Just to clarify, Codewpress is used to manage license details, while recurring payments are handled via Stripe, where subscriptions can normally be canceled directly from the billing portal. That said, we understand this may not have been clear, and we’re checking your specific case to ensure everything is properly canceled.
We’ll continue assisting you via email and make sure this is fully resolved for you.
Forum: Reviews
In reply to: [Prevent Direct Access - Protect WordPress Files] Great protectionHi again,
Just to update here, we’ve located your email in our support inbox and we are responding to you directly.
We’ll continue assisting you via email to get this fully resolved as quickly as possible. Thank you for your patience.
Forum: Reviews
In reply to: [Prevent Direct Access - Protect WordPress Files] Great protectionHi @wildvanvorm,
We’re really sorry for the confusion and frustration this has caused.
If a subscription is set to auto-renew, billing may continue unless the recurring payment is fully canceled. We’d be happy to review your account and ensure everything is properly stopped.
Regarding the email delivery issue, our support address is active, so we’re not sure why it bounced, but we definitely want to investigate this.
Please reach out to us through the support form on our website and include your order ID or the email used for purchase. We’ll prioritize this and make sure it’s resolved promptly.
Thank you for bringing this to our attention.
Hi @dlynch95,
Thanks for clarifying, and no worries at all.
Yes, PDA can work well for your use case. You don’t have to protect files one by one. In the Prevent Direct Access (Gold) version, there is a bulk protection feature available. This allows you to protect multiple files at once.
You can even choose to protect specific file types (for example, PDFs only), so instead of manually selecting each file, all files matching the selected type can be protected in one go. After that, you can set the file permission to allow access only for logged-in users, which fits your client-portal requirement.
So if you’re managing several years’ worth of PDFs, the Gold version would definitely save you a lot of time and effort.
Hi @dlynch95,
If your PDFs are already protected using PDA, you don’t need to set permissions for each file individually. You can go to the PDA settings in your WordPress dashboard and set the file permission to “Logged-in Users”. Once you do this, the permission will automatically apply to all protected files, so only clients who are logged in will be able to access them.
This is a quick way to manage permissions for multiple files at once without having to go through them one by one.
Hope this helps!
Forum: Plugins
In reply to: [PPWP - Password Protect Pages] Scroll down of page when selecting the pluginHi @joostvb,
Thanks for reaching out.
We’ve also replied to your support email with a few follow-up questions.
To help narrow this down, could you please try temporarily disabling all other plugins except PPWP Lite and check if the issue still occurs?
Since you’re using the Divi theme, this will help us determine whether it’s a plugin or theme conflict causing the page to scroll automatically.
If possible, a short screen recording would also be very helpful.
Looking forward to your update.
Hi @nkjackson,
It looks like the protected MP3 is still being served from a server-level cache. This means your hosting server (Nginx or a proxy) is still serving a cached copy of the file. That’s why clearing WP Super Cache didn’t prevent the file from loading.
To fix this, you may need to ask your hosting provider to exclude the _pda folder from server caching. Once that is done, try the protected link again in a private/incognito window, it should then enforce the protection correctly.
Please test after contacting your hosting and let us know the result.
Hi @nkjackson,
Thanks for the clarification, that does help.
The timestamp you’re seeing (Tue, 02 Dec 2025 22:38:13 GMT) reflects when the file was originally uploaded, not when it was protected. If caching is enabled, the server or CDN may continue serving the previously cached version of the file even after protection is applied.
Since you protected the file only yesterday, clearing all active caches (server-level, CDN if used, and browser cache) is especially important so the new protection rules can take effect.
Please go ahead and clear the caches and test again in an incognito/private window. Let us know what you find.
Hi @nkjackson,
Apologies for the formatting issue in my previous reply, reposting the message below.
Thanks for sharing the details.
We checked the links you provided and it appears the protected MP3 is being served from cache. The response is coming from Tue, 02 Dec 2025 22:38:13 GMT, which indicates the file is not being served fresh. When caching is enabled (server, CDN, or browser), protected files may still appear publicly accessible even after protection is applied.
Please try clearing any server cache, CDN cache (if used), and browser cache, then test again in an incognito window.
Regarding the private link (/private/8f31e07fedc842): this is expected behavior. Private links are designed to be shared intentionally with users you want to bypass protection, so anyone with that link will be able to access the file.
After clearing caches, please re-test the protected link and let us know the result.
Hi @nkjackson,
<span style=”font-size: inherit;”>Thanks for sharing the details.</span>
We checked the links you provided and it appears the <strong data-start=”213″ data-end=”257″>protected MP3 is being served from cache. The response is coming from <strong data-start=”287″ data-end=”320″>Tue, 02 Dec 2025 22:38:13 GMT, which indicates the file is not being served fresh. When caching is enabled (server, CDN, or browser), protected files may still appear publicly accessible even after protection is applied.
Please try clearing any <strong data-start=”538″ data-end=”594″>server cache, CDN cache (if used), and browser cache, then test again in an incognito window.Regarding the <strong data-start=”651″ data-end=”667″>private link (<code data-start=”669″ data-end=”694″>/private/8f31e07fedc842): this is expected behavior.
Private links are designed to be <strong data-start=”759″ data-end=”783″>shared intentionally with users you want to <strong data-start=”807″ data-end=”828″>bypass protection, so anyone with that link will be able to access the file.After clearing caches, please re-test the protected link and let us know the result.
Hi @nkjackson,
Thanks for the detailed explanation.
To help us check this properly, could you please share one sample protected MP3 URL from the
_pdafolder? Also, let us know what file permissions are set, as incorrect permissions can cause files to remain publicly accessible.Regarding your concerns:
- With Prevent Direct Access Lite, protection is basic and role-based (Admin or Author only).
- The Disable Right Click feature is intended to prevent common actions like right-click saving or copying links. However, browser features such as
view-source:are handled at the browser level and cannot be fully blocked, so this behavior is expected.
Once we have the sample URL and permission details, we can advise further.
Forum: Plugins
In reply to: [Prevent Direct Access - Protect WordPress Files] ZIP protectionHi @wpandlpuser,
Thank you for reaching out!
Yes, it is absolutely possible to protect .ZIP files located in the
wp-content/uploadsfolder using Prevent Direct Access (PDA) Gold. ZIP files are fully supported and can be securely restricted so only logged-in or authorized users can download them.If you’re looking to protect an entire folder (instead of selecting individual ZIP files), you would need our Access Restriction Add-on, which allows you to apply protection rules at the folder level more efficiently.
Let us know if you need further assistance.
Forum: Plugins
In reply to: [PPWP - Password Protect Pages] lang attributeHi @robodiaz,
Yes, that’s the correct place. The
<?php language_attributes(); ?>inside the<html>tag is how WordPress handles thelangattribute dynamically. You don’t need to add it manually; it will output the correct language based on your site settings.If you want to check what it actually outputs, you can view the page source in the browser and you’ll see something like:
<html lang="en-US">So nothing else needs to be changed in the theme files.
Hi @rvof,
Glad to hear everything is working fine now!
Thanks for the update, and feel free to reach out if you run into anything else.
Hi @rvof,
Just a quick update, our development team has reviewed the issue, and the fix will be included in the next plugin release. Once the new version is available, you can simply update the plugin and the notice should be resolved.
In the meantime, your site will continue to work normally, so there’s no action needed on your side right now.
Thank you again for reporting this and for your patience.