I solved this by making the webserver user the owner and the group of all the files in the WordPress directory. I figured out the webserver user was daemon with: ps aux | egrep ‘(apache|httpd)’ Then I changed the permissions with: sudo chown -R daemon:daemon /your-path-to-wordpress
I think the wp_signon() function is unable to set the login cookies because you are calling it after the page headers have being sent. Try moving your auth code out of dlf_process() and into a separate function like this: function dlf_login() { if ( isset( $_POST[‘dlf_submit’] ) ) { dlf_auth( $_POST[‘login_name’], $_POST[‘login_password’] ); } } … Read more
Dynamically update Site/Wordpress Address
You need to make sure that the folder permissions/ownership are correct. Run this command to set ownership: chown -R apache:apache /var/www/wordpress/
For directory (folder), only read is not enough. You need to set execute also. Because for directory, execute means you can enter the directory. Files need read permission & directory needs read & execute permission. So the directory permission should be: 0555. However, image files inside that directory should be just read, in numeric form: … Read more
GD uses the function imagerotate. According to this answer on stackoverflow the function isn’t included on some OS’es because of a memory leak. This problem is also mentioned as comment in the WordPress code: On some setups GD library does not provide imagerotate() – Ticket #11536 The ticket number belongs to the WordPress Ticket #11536. … Read more
What happen after new plugin get installed in term of permissions?
In my case, these were files in /wp-content/uploads/bb-plugin/cache/ folder.
XAMPP/wordpress heartburn
If your aim is security, the only directory writable by the web server should be uploads. Yes, it means no easy updates, but in a secure environment the web server should not be able to write to directories in which there is executable code. If you have so many updates that SFTP becomes too much … Read more