Update 3.0.4 failed

athriftymom
(@athriftymom)

15 years, 2 months ago

So like many I am having issues doing the auto-update.
First it said it could copy to public_html
then i did the whole delete upgrade folder thing and now it says:
Downloading update from http://wordpress.org/wordpress-3.0.4.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

So now what.. i am too much a of a noobie and scarredy cat to try this manually

Viewing 13 replies - 1 through 13 (of 13 total)

esmi
(@esmi)

15 years, 2 months ago

Are you running WHM on cPanel?

Thread Starter athriftymom
(@athriftymom)

15 years, 2 months ago

yes… but i really dont know much about that stuff. so go easy on me

Moderator t-p
(@t-p)

15 years, 2 months ago

see if these links help:

http://wordpress.org/extend/ideas/topic/cpaddon-for-wp-for-cpanel-one-click-install

http://wordpress.org/support/topic/auto-update-failes?replies=11

http://wordpress.org/support/topic/wordpress-30-upgrade-error-nightmare-finally-solvedfixed?replies=9

esmi
(@esmi)

15 years, 2 months ago

Try changing the FTP server in WHM from Pure-ftpd to Proftp.

Thread Starter athriftymom
(@athriftymom)

15 years, 2 months ago

Yeah so they just did that and I tried to run the automatic update and it doesnt even try to load, now I get this:
Error: There was an error connecting to the server, Please verify the settings are correct.

I had the tech support guys verify that the password and username didnt change, he wrote:
Password didn’t change. I am able to ssh with the same credentials:

any help as to what is happening…

Moderator t-p
(@t-p)

15 years, 2 months ago

tried to run the automatic update and it doesnt even try to load

Looks like your server has issue with automatic update. So try manual update and follow this codex guide. http://codex.wordpress.org/Updating_WordPress

error connecting to the server

-First, double check your wp-config.php file settings for the database name, database username and database password. This is where most errors occur.

-Then check that you don’t need to change the database host from “localhost” to something else. You can get that info from your hosting provider.

-Check you have actually created a database with the same database name as is in your wp-config.php file.

-Last, but not least, if all that information is correct, you may need to contact your web hosting.

codex guide: http://codex.wordpress.org/Editing_wp-config.php

lca7
(@lca7)

15 years, 2 months ago

“t-p” is right,is it work now?

Thread Starter athriftymom
(@athriftymom)

15 years, 2 months ago

Well now I can actually update and the update did go through successfully, My Cpanel and my WordPress passwords were the same.. and the server guys said that wasnt safe, and switched it, maybe there was some new fix on 3.0.3?
i dont know, but ultimately I was updating to get rid of the Auto Draft blog post titles.
Each time i “preview” a post I am working on it says Auto Draft… and if an older post say a week or two old has a link to it that lets say is
mydomain.com/i_like_cheese/

when you click on that link it says not found, although in my post history it is there and published… its like it is assigning new titles for my post after X number of days
any ideas? or should this be a new post?

esmi
(@esmi)

15 years, 2 months ago

New post 🙂

D M
(@eloquentbohemian)

15 years, 1 month ago

There have been many posts initiated concerning the inability for WordPress to be upgraded as of Ver.3. Many solutions have been offered, yet the only one which seems to work is “to change the FTP server in WHM from Pure-ftpd to Proftp”.

I contacted my provider (GeoHost, Canada), with whom I have placed numerous sites on which I have built for clients, both static and on the WordPress platform, and had a long discussion with the senior tech. The solution concerning changing the FTP has its problems in that your provider would have to turn on ProFTP for the entire server, which would significantly increase the memory usage of the server and pose a risk to its stability.

Most people are being hosted on shared servers and altering the FTP for one client, alters the FTP for all the clients on that server, so though it may solve the problem for you, it may cause problems for others.

I reiterate as I have in other posts… the problems are not with the servers/FTP/WHM/cPanel, there is something within the upgrade process which has altered and is not compatible with the afore-mentioned.

I would ask the techs at WordPress why we have never had these problems with versions prior to Ver.3? What within the upgrade process has changed?
As well, why is the upgrade process attempting to create a “directory./public_html” file – and then, after deleting the upgrade folder and redoing the process, does one get “Could not copy file.: /public_html/wp-admin/css/theme-editor.dev.css”?

I have been using my current provider exclusively for over 5 years, and WordPress since the initial Ver.2 on this provider, with no issues on the magnitude of this.

Having to manually upgrade all the sites I have built on WordPress for clients is becoming un-necessarily time-consuming. I do love WordPress and all of its plugins, ease of admin, etc. – but this issue is becoming a major head-ache for those of us who design and manage blogs/sites built on WordPress for clients.

reinard
(@reinard)

15 years, 1 month ago

The problem is not yet solved for 30.0.4 to 3.0.5. The same error:

After the update procedure says »updating the data base« the comes the message after about 1-2 minutes that update could not be completed and to try it some minutes later. What does not work. To reactive the weblog I deletes the file ».maintenance«. After that everything seems to be ok.

I compared all files with the locally downloaded version; they are all ok. But if there remained inconsistencies in the DB I do not know 🙁

It has be mentioned that the upgrade process only fails on STRATO installations. It works pretty on Servers from 1&1. I think it’s up to the WP team to solve that because we are not able to force STRATO and perhaps others to adapt their systems.

pgoodship
(@pgoodship)

15 years, 1 month ago

Ditto, I’m having a really rough time getting this installation to stay stable. my other installation works fine on my other server.

stevem
(@stevem)

15 years, 1 month ago

There is hope for a solution to the upgrade problem, particularly for those people who don’t wish to, or can’t, change the FTP program on the server.

Here are some links to the reasons why this happens and what is going to happen, thanks to dd32:
http://wordpress.org/support/topic/can-not-upgrade-the-newest-version-of-wp (see penultimate post)
http://core.trac.wordpress.org/ticket/10913 (particularly the last 3 posts)

While we wait for dd32’s solution in version 3.2 and hopefully a plugin in 3.1, you can edit some files, upload and then upgrade works and does very quickly.

The changes are listed here http://core.trac.wordpress.org/attachment/ticket/10913/10913.diff but I found I only needed to change two of those files, wp-admin/includes/file.php and wp-admin/includes/class-wp-filesystem-ftpext.php It only takes a few minutes to do.

Those files will be overwritten by 3.0.5 but it’ll only be a matter of seconds to upload the changes again.