WordPress.org

Ready to get started?Download WordPress

Forums

Update to 3.0.4 Failed - Could not create directory.: /public_html (36 posts)

  1. mingswanfoo
    Member
    Posted 3 years ago #

    This is the message appeared when I try automatic update in my 3.0.3 version to the 3.0.4 version. I have tried downloading the file and uploaded it via FTP manually but still no result.

    Any suggestions or comments.... Help....

    Thank you so much in advance.

    I wish everyone Happy New Year!

    Cheers,
    Foo

    This is the message I get...
    ----------------------------------------------------------------------
    WordPress 3.0.4 is available! Please update now.
    An automated WordPress update has failed to complete - please attempt the update again now.

    Downloading update from http://wordpress.org/wordpress-3.0.4.zip…

    Unpacking the update…

    Could not create directory.: /public_html

    Installation Failed
    ----------------------------------------------------------------------
    I installed my WordPress 3.0.3 to my sub-domain through my Host Provider.

    This is the site I am trying to update...
    http://uk.mytrade-community.com/main

  2. fracky
    Member
    Posted 3 years ago #

    i have the same problem.. and instaling plugins too:/ hope we have an asnwer soon.
    Happy new year btw!!

  3. mingswanfoo
    Member
    Posted 3 years ago #

    Hi fracky,

    Hope we get some answer soon.... Happy New Year to you too...
    In the meantime, keep searching around the forum... Hope to find similar post with solution... I'm trying a fresh Manual Install via FTP into another sub-domain... Hope that will work... Will post the result...

    Cheers,
    Foo

  4. That error usually happens when you run out of memory. Try turning off all your plugins before upgrading.

    The problem is that it's a combo of server settings AND your install, so it's not easy to prevent or debug (can't test EVERYTHING after all).

    Or just do a manual upgrade.

  5. Brian1
    Member
    Posted 3 years ago #

    Hello Folks,

    I to am having this problem. I have had my PHP memory limit increased to 64M and I de-activated all my plug-ins.

    Is this a know bug in WordPress?

  6. mingswanfoo
    Member
    Posted 3 years ago #

    Hi Ipstenu,

    Where can I check my memory? Btw, it's actually a newly installed WP... With no plugins at all... Hmmmmmmmmmmmmmmmmmm......

    Cheers,
    Foo

    Happy New Year

  7. Brian1
    Member
    Posted 3 years ago #

    For me I go to cPanel and look at the section "software services" and choose "php configuration". Mine shows directive memory limit 64M.

  8. jpneok
    Member
    Posted 3 years ago #

    When trying to WordPress Autoupdate, make sure that you FIRST:

    0. Delete the Upgrade folder completely from your server
    1. Go into your Plugins page
    2. Click the checkbox above all of them to select ALL plugins
    3. From the pulldown, select DEACTIVATE, then OK it
    4. Try the update again - that usually takes care of the errors for me.
    5. Don't forget to re-enable your plugins as in Steps 1-3

  9. mingswanfoo
    Member
    Posted 3 years ago #

    Mine shows 512M...

  10. mingswanfoo
    Member
    Posted 3 years ago #

    Hi jpneok,

    My WP has no plugins at all because I just installed it...

    Cheers,
    Foo

  11. esmi
    Forum Moderator
    Posted 3 years ago #

    The problem is almost certainly due to your server's configuration.

    http://wordpress.org/support/topic/30-upgrade-bug-ftps

  12. mingswanfoo
    Member
    Posted 3 years ago #

    Thanks esmi, I'm gonna try this right now...

    Cheers,
    Foo

  13. Brian1
    Member
    Posted 3 years ago #

    When trying to WordPress Autoupdate, make sure that you FIRST:

    0. Delete the Upgrade folder completely from your server
    1. Go into your Plugins page
    2. Click the checkbox above all of them to select ALL plugins
    3. From the pulldown, select DEACTIVATE, then OK it
    4. Try the update again - that usually takes care of the errors for me.
    5. Don't forget to re-enable your plugins as in Steps 1-3

    Tried all this and the result was Could not copy file.: /wp-admin/css/theme-editor.dev.css Which has been documented many times in the forums by others.

    Re: the pureftp to proftp issue I have read of people who this has not helped and my service provider claims that proftp is "Not seen this one before! If it is a bug with pure-ftpd then I'm afraid there is no recourse for action; Proftpd is slower, uses more memory and generally has a worse security record so we won't be switching to it."

    So I am back to a wordpress bug.

  14. esmi
    Forum Moderator
    Posted 3 years ago #

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

  15. mingswanfoo
    Member
    Posted 3 years ago #

    Hmmm.... I have a little problem deleting the upgrade directory... scratching my head in the new year! Way to go!

  16. mingswanfoo
    Member
    Posted 3 years ago #

    Keep on deleting the upgrade directory but it's still there.... Arghhhhhhhhhhhhhhhhhhhhhhh

  17. 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.

  18. Brian1
    Member
    Posted 3 years ago #

    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;
    http://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.

  19. 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?

  20. Brian1
    Member
    Posted 3 years ago #

    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.

  21. 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...?

  22. Brian1
    Member
    Posted 3 years ago #

    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.

  23. 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.

  24. Brian1
    Member
    Posted 3 years ago #

    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.

  25. 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.

  26. pixelrage
    Member
    Posted 3 years ago #

    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

  27. *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.

  28. mingswanfoo
    Member
    Posted 3 years ago #

    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)

  29. Brian1
    Member
    Posted 3 years ago #

    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.

  30. 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.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags