WordPress.org

1. designmami
   Member
   Posted 2 years ago #
   

   On my dashboard it said to upgrade a Personal theme, so I did.. after that.. my site was gone. i updated all the files again...and it asked me to upgrade the WP again... and this is what i got

   now I cant even access the site :((
   Please help!

   Downloading update from http://wordpress.org/wordpress-3.0.zip%e2%80%a6
   Unpacking the update…
   Verifying the unpacked files…
   Installing the latest version…
   Could not copy file.: /public_html/x/wp-admin/css/theme-editor.dev.css
   Installation Failed

   after this... everything is gone. thiw is the website : http://www.kakii.com

   thanks in advance

2. mrmist
   Forum Janitor
   Posted 2 years ago #
   

   Download the zip file and upgrade manually, as your automatic upgrade did not work.

3. designmami
   Member
   Posted 2 years ago #
   

   i did that.. i will try again & post what happend.. ty

4. designmami
   Member
   Posted 2 years ago #
   

   ok so i did it again.. i go to

   /wp-admin/upgrade.php

   I get this:

   No Upgrade Required

   Your WordPress database is already up-to-date!

   I click continue.. and I come up to a blank page :(

5. designmami
   Member
   Posted 2 years ago #
   

   I can get to my cpanel... but Im gettin this msg on top again

   "An automated WordPress update has failed to complete - please attempt the update again now."

   I did that b4.. and it went all blank /...

   Help :(

6. mrmist
   Forum Janitor
   Posted 2 years ago #
   

   Did you do the manual update process or not? I'm talking about the whole thing not just visiting the upgrade page.

7. designmami
   Member
   Posted 2 years ago #
   

   yes I did all the instructions from Manual Update page.

8. designmami
   Member
   Posted 2 years ago #
   

   This is crazy thou.. BC I did all the upgrades automaticaly b4 and it worked perfectly fine. Now it asked me to update this theme & it crashed my whole site :(

   And all my other themes are gone now too.. the ones that were all customized :(

9. designmami
   Member
   Posted 2 years ago #
   

   Ok now i got the site up.. but I got this MSG again at the top of my Cpanel
   
   "An automated WordPress update has failed to complete - please attempt the update again now."

   I did this b4 & everything crashed.

   Any suggestions?

10. wp-leona
    Member
    Posted 2 years ago #
    

    I've got the same issue, so why has auto update failed and how do I update?

11. jaksalee
    Member
    Posted 2 years ago #
    

    @designmami

    Same happen to me. Still can't update it, i also did the manual upgrade and this msg still occurs: "An automated WordPress update has failed to complete - please attempt the update again now.".

12. dandick
    Member
    Posted 2 years ago #
    

    I got the public_html/x/wp-admin/css/theme-editor.dev.css message
    when I tried to update http://www.save-your-marriage.org automatically. However, the manual update worked fine for me.

    What I did was basically what I remembered doing when I upgraded to 3.0.

    I deleted the old files first, keeping
    wp-config.php as it contains the configuration data
    wp-content as it contains the themes, plugins, etc.
    images as it contains pictures I uploaded

    Then I selected everything but those three items from the new wordpress directory and recursively copied those into the root directory of the website. Also, if the .maintenance file was there, I removed that, too so that the website wouldn't keep coming up with the maintenance message.

    I then ran the upgrade.php, clicked the button to update the database, and everything came up working fine.

    Anyway, this site was set up to be a plain WP site and not WPMU.

    I just ran an automatic update on http://save-marriages.com which I set up as a WPMU site on a VPS, and the upgrade went almost perfectly.

    I say almost because it came back saying the upgrade was successful. However, when I pressed the dashboard button, I got a white screen! Yikes. I held down shift and pressed the refresh button on my browser and the dashboard came back.

    Just to make sure things were consistent, I cleared my caches on the sites after doing the upgrade.

13. nz1m
    Member
    Posted 2 years ago #
    

    I run a cpanel-based web server with a dozen or more wordpress users. ALL have the same prob with 3.01 upgrade. First it's the /public.html problem then the css problem. I've updated PHP Upload Limits to 10 megs. I've chmod 777, removed and reinstalled /upgrade chomd'd 777... all the suggestions. Nothing works. Manual updates are a PIA and require excessive unbillable time. I'm recommending my users stay with 3.0. I additionally find the WP updates come way too often. Every other week there is a Dashboad Upload "demand" and it's annoying, often unnecessary, time consuming, and - in this case - extremely problematic.

    Enable Dashboard "turn off notifications". When a major release is required then we'll deal with it.

14. achshar
    Member
    Posted 2 years ago #
    

    HEy yes i have EXACTLY the same error everytime i update my blog..
    now my blog is completely blan.. nothing at all just white.. even the vier source brings up a white page with no html at all..! this is so annoying plus i completely agree, wp rolls out updates quite often.. i am stuck with updating my wp every week.. every Fing week..! this is SOOOO annoying..
    please help me with the above error
    i got this error so i manually updated my wp.. deleted every file (obviously not the wp-config and databases) and then extracted the new files in the same directory and went to wp-admin/upgrade.php.. it told me that database need to be updated, and it updated the database... next it took me to homepage which waas blank completely blank.. the whole blog is down but dashboard is still accessible.. i really would have preferred the other way around..

    After my recent experience with wp upgrades.. (mannually installing my wp 3 times which lead to my settings, themes widges and almost evey change go away and that too for small upgrades.. like from 3.0 to 3.0.1!) I PROMISE I WILL NOT UPGRADE MY WP UNTIL IT REACHES 4.0

15. SirLouen
    Member
    Posted 2 years ago #
    

    Same error here... all was set to 777... I believe that automatic upgrade are not really well functioning.

    I was wondering how can I solve this issue.

16. sunrise3
    Member
    Posted 2 years ago #
    

    won't upgrade themes seems not worth the risk and have no plugins installed but 3.0 to 3.0.1 just worked fine automatic

17. mrarung
    Member
    Posted 2 years ago #
    

    I have a same problem here

    When upgrade automatically I have some error:

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

    Unpacking the update…

    Verifying the unpacked files…

    Installing the latest version…

    Could not copy file.: /public_html/wp-admin/css/theme-editor.dev.css

    Installation Failed

    When I visit my site Vimax

    Briefly unavailable for scheduled maintenance. Check back in a minute.

    Before it was no problem when upgrade automatically but after I move to other hosting it should to put password before upgrade automatically, so I think I have to try upgrade via cpanel, I hope it's working properly

18. mehulv
    Member
    Posted 2 years ago #
    

    I am having the same issue, when upgrading from 3.0 to 3.0.3 on two of my sites.

19. Ekine
    Member
    Posted 2 years ago #
    

    same error here. Why do so many users have the same problem? What is causing this problem?

20. mehulv
    Member
    Posted 2 years ago #
    

    I upgraded using FTP, and it worked without any problems.
    A little more effort but a simpler way.

21. fatdiver
    Member
    Posted 2 years ago #
    

    I've had the "Could not copy file.: /public_html/x/wp-admin/css/theme-editor.dev.css" problem for a few upgrades now and have been manually updating. After trying everything I could think of to get the automatic update working again, I finally cracked it - by paying attention to the article about upgrading: http://codex.wordpress.org/Upgrading_WordPress

    Note that your files all need to be owned by the user under which your Apache server executes, or you will receive a dialog box asking for "connection information," and you will find that no matter what you enter, it won't work. See man chown. If you do not know which user runs the httpd the output of ps auxw | grep -E 'http|apache|www' or ps auxw might help, see man ps.

    My apache server is run by the user 'nobody'.. As soon as I changed my public_html folder recursively to change owner to 'nobody' - the automatic upgrade worked straight away.

    Here's what I did via SSH (although I'm no expert)

    cd /home/(whatever-your-domain-root-is)/public_html
    chown -R nobody .

    Basically get to your public_html folder, chown is 'changer owner', -R makes it do all folders and files in the installation, and the full stop at the end means it'll avoid system files with two full stops in them

    This may not be the best/safest way to do things (like I say, I'm no expert), but this worked for me

22. Severisth
    Member
    Posted 2 years ago #
    

    Ugh, same issue again with 3.0.3. I have yet to have an automatic upgrade work. Alas.

    Off to the manual upgrade.

23. moneypumps
    Member
    Posted 2 years ago #
    

    I get the same error. Nothing works.

    I have tried deleting the upgrade folder and recreating it and also manual install. The blog seems to work fine, except I cannot upload files or plugins. But the error message can be seen by all members.

    Is there a way of removing that error message? As my blog is still functional, any attempt to fix the error fail, and I know that the upgrade went wrong, it does not need to display.

24. daninm
    Member
    Posted 2 years ago #
    

    I just upgraded to the WP 3.0.3 and all of a sudden have dots along the left hand side of my blog above and below each post and page. Happened to anyone else? Thoughts?

    (You can see it on http://www.danimcgrath.com)

25. gladman
    Member
    Posted 2 years ago #
    

    I had all the same problems listed here - from the public_html file to the css file stalling out both my blogs. The amazing ladies running Hosting Matters sent me this email to solve the problem:

    Nah, nothing that complicated, just WordPress' inability to deal with the pureftp server we've been using. I've changed the server over to proftp, it should work fine now.

    That solved all the above issues for me. If you need a super responsibe host, try hostingmatters.com I've been with them for many years.

26. xxxxxcata
    Member
    Posted 2 years ago #
    

    @gladman proftp works like a charm!
    If you guys have an whm, consider to install proftp

27. John Ford
    Member
    Posted 2 years ago #
    

    If anyone is still running into this issue there's a patch (http://core.trac.wordpress.org/ticket/10913) for WordPress that should go into 3.2. In the meantime, there's a plugin that should help fix updates for most of you: http://wordpress.org/extend/plugins/ftp-upgrade-fix/

28. Tom
    Member
    Posted 2 years ago #
    

    Same issue with a FRESH install of WordPress. Very first thing I tried to do was to upgrade to 3.1.1..

    Downloading update from http://wordpress.org/wordpress-3.1.1.zip…
    Unpacking the update…
    Verifying the unpacked files…
    Installing the latest version…
    Could not copy file.: /public_html/wp-admin/css/theme-editor.dev.css
    Installation Failed

    Stuck in maintenance mode (I know how to get it out of it).

    To be quite honest, I've used WordPress for a long, long time but NEVER managed to successfully auto-upgrade it. Manual upgrade takes too much time (especially when you have over 30 sites to upgrade!)

    Any real solution without having to change server config?

29. nickjo
    Member
    Posted 2 years ago #
    

    http://wordpress.org/extend/plugins/ftp-upgrade-fix/installation/

    Try that.

30. efeervescente
    Member
    Posted 2 years ago #
    

    this fix doesn't work for me, try this: http://wordpress.org/support/topic/how-to-fix-the-autoupdate?replies=1#post-2085286

Topic Closed

This topic has been closed to new replies.