Hardening WordPress on the WordPress Codex is a very good article on how to secure your WordPress blog, which goes into quite some detail on file permissions, as well as some other methods of securing WP.
Lock access to plugin options
Your files should be owned by your account. Period. They should not be owned by the “apache” user. This is insecure. The files may need to be readable by the apache user. The recommended permissions are 755 for folders and 644 for files. With the exception of the wp-config.php file, which should be set to … Read more
Filtering results for post_type tells me I don’t have permission
Tetsu, the Codex has some good insights on this: http://codex.wordpress.org/Changing_File_Permissions Unfortunately there is no ‘one size fits all’ according to the Codex. It may depend on your host.
It seems unorthodox but I added my user to the _www group: $ sudo dseditgroup -o edit -a ‘whoami’ -t user _www Finally, I gave write privileges to the group: $ sudo chmod -R g+w /path/to/dir That seems to work, but like I said seems like a weird solution to add my user to the … Read more
Have you had a look at is_user_logged_in()? If you can explain how you’re serving the photos I can perhaps suggest a way to authorize some images to be shown and the rest hidden to only logged in users.
Grant user rights to access certain tabs of a plugin
Make sure your disk space quota has not been reached. I had the same issue, and had to remove some old files to stay within the limit or just raise the disk space quota for the account. I left all the original file and folder permissions the same as that didn’t feel like a logical … Read more
Just because I added the question here, I found it … So … easy… so irritating… but I hope this answer will help anyone else with this issue quicker! changed ‘hierarchical’ => true to ‘hierarchical’ => false for the custom post type!