netsolution

same problem here… I will try to contact the hoster.

Yes sure I meant “chown” – sorry for that, can not even modify the post anymore to fix that

It also worries me that I have not yet found the underlying cause for the whole thing.

It still a problem having to chown all files before doing a core upgrade or even a plugin upgrade (or having to delete the .maintenance file if you don’t want to have the page inaccessible for 10 minutes)

Currently about 50 WP installations are affected by this here – so I need to find a definite solution for this to get back to the one click upgrades.

As I said all other WP instances (on wheezy distributions and SuSE distributions) work without any problems.

Do you all use FTP mode for the upgrades etc.?

Did anyone file a WP bug yet?

I use Wordfence on the affected sites, but not Cloudflare.

I tried disabling Wordfence, but that made no difference.

I run VSFTPD on Jessie, thats why I need FTP to update, so the necessary ftp access information is in wp-config.php.

I noticed that the WP upgrade file is downloaded, extracted and then deleted again (I see the deletion commands in the FTP log) – so it does not seem like extraction is not working.

Owner of webserver created files is www-data – owner of ftp created files is the virtual server owner (username = domainname)

I have noticed that the WP core update works when I do

chmod -R www-data /home/mydomain.com/public_html

run the update (works fine), then

chmod -R mydomain.com /home/mydomain.com/public_html

to get the original permissions again

So as far as I can see it must be some permission problem when using FTP ext instead of direct access, and this was introduced in 4.5 or the version before 4.5

Additional information: I use Virtualmin to manage the server.

That’s my input for now…

I also noticed that WP does not remove the .maintenance file after upgrading plugins anymore.

This happens with each update of a plugin (and not only if an update fails).

Before the 4.5 version this has never been a problem.

Did anyone solve this or the other problem mentioned above (inbox update to 4.5 failing)?

Thanks

I know that I can upload that manually via FTP – but still upgrade via backend is not possible, and this is strange!

I am interested why it is suddenly not working anymore for 4.5

I also have this problem for the first time, it affects all 20 WP sites on one specific Debian Jessie server only.

Before 4.5 updating WP from backend always worked without any problems on this server.

Anyone has an idea how this can be solved? Let me know….

Hi

Yes, that change fixed the problem.

Am I the only one with this problem? Strange…

Thanks!

Thanks – everything works fine now!

Sent you a donation as pomised….

Thanks – same situation – directories get created but .css not written.

I can give you access to one of my wordpress installations if you want.

Hi

Thanks for moving the folders to uploads, I think that is where they belong and where most other plugins put their stuff.

But unfortunately the plugin does still not write the .css file to the my_custom_css folder.

Permissions for the folders are correct, but no css file inside them.

in the editor there is a lot of css!

but there is 1_1446628307.css in the /bkk folder

nothing in my_custom_css folder, no matter how many times i click “save”

very strange.

I did

touch my_style.css
chmod 666 my_style.css

then I click “save” in the my css settings page –

and the my_style.css file is deleted again – empty folder!

the permissions are 777 – but still no .css file gets written to the folders.