That seems to be a server issue. All I can suggest is that you consider upgrading WordPress manually.
Thanks for the fast response.
My issue also applies to themes and plugins.
A manual upgrade is always lot of work. If it will work afterwards then it might be OK. Due to the fact that I have seen such an issue more often, fixing the issue and auto updating afterwards would be a better option for the long term.
Any ideas how I can fix it without the manual update option.
Thanks.
Since this issue is nothing to do with WordPress, there is nothing that can be “fixed” at the WordPress end. Try contacting your hosts about it.
@esmi
thanks a lot for your help.
This is not a problem of the host which I might have not describe detailed enough.
The setup is as follows:
+ one Host (Server)
+ Installed OS Ubuntu
+ One Apache running
+ One DB running
+ turning off SELinux and rebooting afterwards does not make any difference and there are no messages when SELinux is in permissive mode
This is all and all installed software on that server is the same for both installations.
On one the buildin upgrade and reinstallation is working and on the otherone it is not. I do not understand why this should be a problem of the host.
I hope that there are other people which are able to help.
I just installed 3.6.1 on the same server same directory and adjusting Webserver rights.
Reinstalling with the build in option is possible now, hence it has to to with wordpress. I will investigate further to get closer to the issue.
This problem appears to related to the files that WordPress has available for download. We’ve ran into this same exact error on 80% of the websites we manage, all on different servers/configs.
WordPress 3.6.1 has been downloaded over 9 million times but only you two seem to have this problem. Now, in your opinion, would this suggest an issues at wordpress.org or an issue with your sites?
[Moderated]
@world
here is the way i fixed it:
- take a backup of your broken WordPress installation (e.g. copy it to your PC by using ftp, sftp, scp, etc.) or take a local backup of your broken WordPress e.g. by using tar (tar cf wordpress_3.6_broken.tar <your wordpress directory>
- It is very important to have a copy of wp_config.php, .htaccess (if you use it) and wp_content
- Move your broken WordPress installation aside e.g. mv wordpress wordpress_3.6_broken but remember the directory name in this case “wordpress”
- Create a directory for wordpress_3.6.1 in my case it is called wordpress by using e.g. mkdir wordpress
- Copy WordPress version 3.6.1 your server into the created directory.
- remove wp_content from your new installation
- copy wp_content from your backup into the new installation directory e.g. mv wordpress_3.6_broken/wp_content wordpress/
- copy wp_config.php and .htaccess to the corresponding directories of your new installation e.g. mv wordpress_3.6_broken/wp_config.php wordpress_3.6_broken/.htaccess wordpress/
- Make sure that all file have the right ownership e.g. apache
- Open your browser and login to WordPress and go to Dashboard>Updates and klick on Re-install Now. This should now work without any problem.
- Now you can update your plugins, like always.
Hope everything went fine for you as well! If not make a restore of your former taken backup and you are back in Business but with the old problem.
A manual upgrade (as suggested 2 days ago) would have also have fixed it.
But much more work. 🙂
If I have had 2 equal versions I would have provided the diff to you.
Invested time in looking for an solution had been 3 hours. Manual upgrade with taking care of every bit and piece would have taken longer. Meanwhile I have dated 4 WordPress installations that way.
Now I have a way which is very easy and takes just a few minutes and will save much more time on the long run.
But much more work.
No. Only about 4 steps (including backups) compared to your 11 steps and would probably have taken about 10 minutes tops.
