Update to 3.0.4 Failed – Could not create directory.: /public_html

The folder gets recreated when you run an upgrade. S’allright.

I hate to say this but not EVERY host allows the automated upgrade to work. Do it manually.

I’m personally convinced that this is a server owner/permissions problem. Do you have access to the server’s error logs?

But the process is failing in the copying of files from the upgrade folder to the installation part way through. The files that it is copying over are all the same permissions and ownership.

Check out this screenshot;
https://www.burtsgh.com/dl/ScreenShot032.gif

You can see this is a section of the css folder where the installation fails and all permissions and ownerships are identical.

Yeah, there’s more to ownership than who owns the files, it’s what groups the ID being used to DO the copy are in, and what permissions THAT ID has.

For example, not at random, did you know that some servers use your ID (brian1 let’s say) to copy over, while other use a specific web-server ID?

So since the ownership/groups/permissions are all the same for these files the implication is that the WordPress installation changes its ID?

Please note the last column in the screen capture is the user and group.

So the user and group for all these files are the same.

So since the ownership/groups/permissions are all the same for these files the implication is that the WordPress installation changes its ID?

Not WordPress. The implication is that the ID being used by the SERVER when PHP is called BY WordPress is what has the wonky perms. Semantics. I know. They kinda matter ??

What kind of server are you on? *nix Apache or IIS or…?

I am using a shared hosting package with Net_Hosted in the uk. It is a Linux apache installation.

So why would the servers response be unique in this regard (IE the server changes IDs when a process is called by php half way through execution of the process).

I have used Concrete5 (cms), Filezilla and the cPanel file managers and they do not have issues with changing ID during processes.

So why would the servers response be unique in this regard (IE the server changes IDs when a process is called by php half way through execution of the process).

S’not unique. The server is not changing IDs midway. It’s that the ID being used doesn’t have permissions to do what it needs. Why does it happen on SOME files and not others? Well, PHP can be a royal *(#!@&* sometimes ??

Filezilla and cPanel are not using PHP to upload files. I promise.

Shortest version of all this: PHP gets screwy, it’s not WordPress per se, even though that’s where you’re seeing the problem.

To fix:
1) Delete EVERYTHING except
wp-content
wp-config.php
.htaccess
(and if you have it robots.txt)

2) MANUALLY upload the WordPress files

Should be okay going forward from there, though some of your plugins may not be so happy.

So if not a WordPress bug this sounds like Wordpess using an unreliable process ie. php for file transfer?

….with the resulting conclusion being that the automatic update is not a reliable process.

Oh heck, the automatic update is a mostly reliable process ?? It’s using PHP, and that IS reliable, it’s just not installed the exact same way on every single server out there, y’know. When you take into account the variables of servers (apache, ngix, iis, etc), the myriad versions of PHP (from 4.2 to 5.2 these days…) and everything else (permissions given to php, php-cgi vs fast cgi, caching software, OS versions, etc etc) it’s almost a bloody miracle that it works 80% of the time.

And it does ??

Bog standard response. If the AUTO upgrade fails, do it manually.

I have to say, I’m a bit pissed off at how this is happening. I simply can’t auto-upgrade WP at all anymore. I’ve been using WP for about 5 years now and have never seen such an issue before. Nothing I do resolves it. It’s not my server. It’s not the /update folder issue. It’s not my active plugins.

Once again, I’ll do a manual upgrade, but it begs the question, what is the point of the automatic upgrade if it does not work. Ever since 3.0.3, all updates had to be manual, and it’s an atrocious pain in the ass when you are running 10+ WordPress sites…

/rant

*sigh*

Because it does work. Most of the time. For most people. But not you. Which sucks. I know. And I’m sorry about that too. Doesn’t work for me on one site reliably at all, and works fine on another. I ended up writing a bash script to do it for me.

If you can fix it so it works 100% of the time for everyone, I promise you puppies and sunshine will rain down upon your head. But no one’s managed that yet. And I doubt they will. You can’t make something work flawlessly 100% of the time on 100% of the severs, given the infinite variables and combinations involved. It’s just mathematically impossible.

Hmmmmm………. Just tried to install manually but….

Fatal error: fatal flex scanner internal error–end of buffer missed in /home/mytradec/public_html/CA/wordpress/wp-includes/functions.php on line 4198

I’m so pulling my hair… I’m going on holiday in an hour and I’m still in front of my laptop!

Man!!! I’ve been trying to solve this issue LAST YEAR!!! (LOL… Last night)

Shortest version of all this: PHP gets screwy, it’s not WordPress per se, even though that’s where you’re seeing the problem.

Saying PHP “gets screwy” is not really an explanation. And it seems to me that suggesting it is a permissions problem when the ownnership and permissions are identical for all files is not either.

The problem with simply suggesting that it is because PHP is unreliable is that the whole system is based upon PHP.

mingswanfoo – Did you delete the folders wp-includes and wp-admin before you tried to manually upgrade?

It sounds like your FTP client isn’t copying everything up.

Brian1 Since we’re not helping the OP (mingswanfoo) with this, I suggest you make a new topic in the Misc. area and bring it up in general. But at this point, if you can’t understand that I’m saying it’s a mathematical impossibility for this to work 100% of the time on 100% of the variations of servers, then I can’t help you at all.

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