New answers tagged

0

I have discovered the problem. Documentroot in apache has changed, so updating this has fixed the problem


2

Not a direct answer, but probably has to be said - this is one problem you should avoid solving unless you are talking about a local development in which case you can just set permissions to 777. The reason is that if the webserver can overwrite your code, then any malicious code running on it will be able to do that as well. The risk is just so much bigger ...


0

So I contacted DigitalOcean who told me to do the following which solved my issue: We recommend removing the changes you made to wp-config.php to start. Once done, please try issuing this command: sudo chown -R www-data:www-data wordpress Just change 'wordpress' to the directory of WordPress installation, and see if that works to waive the ...



Top 50 recent answers are included