3.0 Plugin Upgrade Bug? Could Not Create Directory

Cool, just checked, my welcome message states Pure-FTPd! Thanks, im glad I could confirm that.

esmi – Would changing the ftp server change the path settings? I didn’t make any specific adjustments to the path, but on my servers, installing proftp definitely works, and using pure-ftpd definitely doesn’t.

Are your installations manual or do you use fantastico? I wonder if fantastico-installed file permissions/ownerships might be different from the “default”.

It would be interesting to find out what all the folks having issues have in common… fantastico? a certain OS? a certain plug-in? etc…

I have wordpress running on 4 different server/location. All server using pureFTP but only 1 host giving me that kind of problem.

so i guess, its more to configuration/setting problem on the server.

i just installed another wordpress on cpanel pureftp via softaculous and working great!

so i guess, its more to configuration/setting problem on the server.

That’s my best guess too. Had a little chat with my hosts and they’re convinced that it’s going to be a folder/file permissions or owner problem.

I just tried two auto-upgrades, different cPanel accounts, same configuration, same VPS.

From 2.9.2 to 3.0.4 (yeah yeah, i know) – it zinged right through, no pauses, no errors.

From 3.0.2 to 3.0.4 – after the usual 2 minute hang on “Installing,” it died at the usual spot (wp-admin/css/theme-editor.dev.css)

I realize this is just one data point, but almost every thread on this issue seems to describe a 3.x to 3.x upgrade. Is there any way we can definitively confirm/deny that this is not some aspect of the version 3 upgrade process or file structure?

And has anyone taken a good hard look at theme-editor.dev.css? Cause I am starting to develop an irrational hatred that file.

And has anyone taken a good hard look at theme-editor.dev.css? Cause I am starting to develop an irrational hatred that file.

I am too having this problem. And no solutions yet, many are waiting solutions for this issue as they do automatic upgrade.

i changed the pureftp to proftp in whm panel ftp server sellection page. all problem are fixed

My hosting guy said that in shared hosting changing to proftp is not possible.
Any ideas

@oulos70: Are you using the WHM within cPanel?

@esmi Yes. I have WHM and cpanel accounts

I’m beginning to think that the issue may lie within WHM and Pure-ftpd.

I ran two more auto-upgrades on the same server (LiquidWeb VPS, running pureFTP) with installs in separate cPanels:

2.9.1 -> 3.0.4 = upgraded with no error
3.0.1 -> 3.0.4 = death file (theme-editor.dev.css)

On this server at least, the pattern is consistent. Plugin updates run fine. 2.9.x updates run fine. 3.0.x upgrades fail in exactly the same way.

Has someone fix the WP auto update problem with pureftp (is it the problem?)
Regards Paula

Success! I tried almost all of the solutions (including recreating the upgrade folder and changing permissions) but none of them worked.

The solution that worked for me was to change from PureFTP to ProFTP inside of the Web Host Manager (root) interface. This can be changed in WHM Main >> Service Configuration >> FTP Server Selection.

If you are on a shared server and do not have access to WHM, try contacting your hosting company. I also have a WordPress install on a shared server for another site I run, but the auto update worked fine there. I was having problems on my own server at a different hosting company.

Do anyone know why PureFTP is the problem with WP autoupdate?
I cannot change the ftp pureftp service!
I can suggest a solution to the hosting provider to patch pureftp?

Do WP 3.0.4 solve this problem?

Regards.