How Photography Management protects your images
If you upload an image via Photography Management, it will be stored in a specific folder on your server. Every request from the internet to this folder is scanned and evaluated by Photography Management. If the user is not permitted to see the image Photography Management will block the access. However, this only works for images which were uploaded via Photography Management. Thus,
upload all images via Photography Management for proper protection.
For most servers the image protection works out of the box, but not for all. Basically, the server must redirect the requests from the folder to a specified URL. This URL is usually defined in the file
wp-content/uploads/photography_management/.htaccess on your server. Thus, an Apache server has so support/process
.htaccess files and the mod_rewrite module enabled. Again, this is given for most commercial servers out of the box.
If you have a commercial nginx server the chance is high that the redirect also works properly for you. Because on the one hand nginx servers usually need fewer resources (which is good for the host), but on the other hand it is less configurable which increases the support overhead. Therefor, the hosts often automatically translate the Apache config file
.htaccess to an nginx configuration.
Testing if the protection works on your server
If you want to test whether the protection works for you out of the box, follow these steps:
- Create a client and password protect her
- Create a project and upload one image to the gallery via Photography Management
- Update the client
- Go the media library and copy the image’s URL
- Logout from your WordPress site
- Enter the image URL in the browser
If you see the image, then the protection does not work out of the box, you have to consult your host. Otherwise, everything is fine!