I found the answer, dropping it here in case someone need it. You need to be logged in as a user that has the edit_posts capability. With that capability, you also get access to the private query vars, including post_status. Taken from this similar issue.
Just because you have write access from the ftp user doesn’t mean that the user Apache/PHP is running in has write access. I’d advise you upgrade manually, or check your write permissions and ownership for whichever user Apache is running as on those files.
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.
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
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
Grant user rights to access certain tabs of a plugin
In the end I went with XAMPP and the WordPress Bitanami application. I have yet come across any issues with file permissions and managed to setup virtual hosts with the help of this tutorial.
Should Apache own /var/www/domain.com directory in WordPress?
Your file and folder ownership seems fine at the beginning. Simply update your wp-config.php file with this line: define(‘FS_METHOD’, ‘direct’);
Invalid changeset UUID WordPress