Chris Dennis

That seems like a reasonable fix, but I don’t use WordPress any more, so I’m not able to do any maintenance on this plugin.

Feel free to take ownership of the plugin if you want to.

Thank you.

For those other file types, you need to tell the browser how to open them. There are various discussions online about this, for example https://stackoverflow.com/questions/48860620/which-file-types-can-be-viewed-in-browser-inline-without-a-plugin

This WordPress plugin isn’t involved in that process.

Cheers,

Chris

Resolved

Resolved

Hi

Thanks for your question.

No, this plug-in checks to see if the user is signed in before allowing access to private files — it’s not related to password-protected pages.

Regards

Chris

If a visitor tries to access an image (or other document) on a private WordPress post, then the site can prompt for a log-in if required — there are various ways to do that in WordPress.

But an image attached to a private WordPress post can be accessed directly by anyone who knows or guesses its URL. That’s the issue that the Private Uploads plug-in addresses.

You’ve made me think about whether the server should return a 404 (‘not found’) status code instead of 403 (‘forbidden’). As you say, the latter implies that the item exists.

Hello

I can’t check what’s wrong with that image because it’s private! — I get a 403 status code, which is exactly what should happen.

And I can’t check your Apache settings because I don’t use Apache — the rewrite rule was provided by a contributor.

It’s possible that imgbox.com is doing something to the URLs that is breaking things, because the link you gave doesn’t show ‘uploads’ or ‘private’ anywhere in the URLs for the images. That’s out of my control, I’m afraid.

Hello Arturino

No, I am afraid that Private Uploads does not have that ability.

I don’t have any problems with MP4 files in the private folder, so I think your issue must be related to the theme that you mentioned.

I don’t have any problems with MP4 files in the private folder, so I think your issue must be related to the theme that you mentioned.

You need to find out from Bluehost whether they use Apache or Nginx or something else.

If it’s Apache, then there are instructions for this plugin at https://www.ads-software.com/plugins/private-uploads/#installation which tell you how to put the relevant rules into a .htaccess file.

Nginx doesn’t have an equivalent to .htaccess files, so you’d need access to the main server configuration files. You’d need to ask Bluehost if that’s possible.

I hope that helps.

Hi. Thanks for your question, but the answer is “No — it doesn’t work like that.”

The web server only sees the address that you’re currently connecting to the browser from, by referring to PHP’s $_SERVER[REMOTE_SERVER] variable. That will only be either IPv4 or IPv6, not both (as far as I know), even if you currently have two connections to the internet.

OK, thanks. I don’t see the error message that you’re getting, so I can’t tell what’s causing it. Which log file does it occur in, or does it appear on the browser?

Could you try enabling debugging in WordPress (see https://codex.www.ads-software.com/Debugging_in_WordPress) and let me know what appears in wp-content/debug.log?

Hi

Please can you send me some more details of your problem?

What version of the plugin are you using? Are there any more error messages before or after the one you mentioned?

Regards

Chris