Hi my friends, it’s possible to did this with this plugin?
https://www.consultoriodocondominio.com/wp-content/uploads/2017/01/area-cliente-Copy.png
]]>This functionality should be in the core but isn’t. So if you can update this for new users would be great. Thanks.
Kris
]]>I tried using this plug-in to protect files in a multisite sub-site, but it failed to work. The plug-in description says an .htaccess file would be uploaded to the uploads directory, but multisite stores sub-site uploads in a folder called “files” under blogs.dir, so perhaps that’s the root of the problem?
]]>I installed the plugin, and clicked “protect” in the settings and nothing happened. I clicked on “reprotect”, and now I get an error 500 on all my pages:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@[domain] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
]]>Is there a way to get this to work with WP3 multisite? It seems to not work with the root htaccess file’s url rewriting for the subsites.
]]>[Plugin: Private Files] Gives server error 500
]]>Hi Guys
I have installed the plug in and activated it, but when I click ‘Protect’ nothing changes, the control panel still says ‘Unprotected’.
Why would this occur? It seems like such a simple plugin…
Thanks
]]>Summary:
After files are protected all pages (Pages, Posts, Files, Admin, etc.) return a server error 500. Editing the .htaccess file fixes the 500 error (see below).
What I did:
After installing and activating the plugin, I went to “Tools > Private Files” and selected “Protect” for any of the dropdown selections. A yellow update box said that files were protected, but all files were still accessible when not logged in. After selecting “Reprotect” the server gave 500 errors to any web page accessed.
How I reversed the problem:
Since the plugin page says to remove the .htaccess file, I tried that first. This does fix the 500 error, but disables mod-rewrite and makes every Post (Posts and Pages) give a 404 error.
To fully reverse problem, I added this back to the .htaccess file (it was taken from another WordPress install, and is pretty standard):
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPressMy thoughts:
It appears that two things happen:
1: The .htaccess file is written over improperly, removing a necessary rewrite rule.
2: The new .htaccess file assumes the proper file structure incorrectly. I.e., it adds “RewriteBase /wordpress/wp-content/uploads” which assumes the WordPress install will be in /wordpress/ which is not true in many (most?) cases.