Update 4.7 always stuck…

Hi Dave,

Can you firstly make sure that you’ve gone through the update checklist on this post:
https://www.ads-software.com/support/topic/read-this-first-wordpress-4-7-master-list/

If the auto-update continues to fail, do you have FTP access to do a manual upgrade?
https://codex.www.ads-software.com/Updating_WordPress#Manual_Update

And we are having full access to he server, but without anything in the logs, I can’t do anything… Enabled debugging, nothing special in logs, so could it be connected to wrong php.ini configuration? Or something else?…

https://www.ads-software.com/support/topic/read-this-first-wordpress-4-7-master-list/ I’m sorry but this is a list, for people, who already updated to 4.7… we CANT update to 4.7

There are a number of different reasons why automatic updates might fail, and it can be hard to debug from a support perspective.

Whilst it takes a little longer, if you have full access to the server I would suggest manually upgrading your WordPress site using the instructions here:

https://codex.www.ads-software.com/Updating_WordPress#Manual_Update

The thing is, i want to fix that, also for future updates…
So i dont really like to update manually… some other ideas? Is there a support, which i can send the login infos?

I understand that you would rather fix it for future updates. Unfortunately we are unable to provide support by logging into your system.

You could try increasing the maximum execution time in the php.ini file, as it may be a timeout problem the update script.

However, I am hoping that the issue was a permissions problem (which is often the case with auto-update errors), and by upgrading manually it may fix it for future updates.

Im having the issue in both wp installations… max exc time is already on 300 for my avada theme…

I am having the same issue. After updating to WordPress 4.7. I found on Forum READ THIS FIRST WordPress 4.7 Master List that: W3 Total cache – Version 0.9.5.1 is incompatible with WordPress 4.7and it must be deleted entirely. I did this on 2 other sites and update worked fine. Unfortunately I did not remove it from 1 site and am going to try to restore a back-up to see if I can remove it. If anyone has any ideas on how to remove W3 post update, that would be very helpful.

I am having a similar issue. The upgrade looks like it completes successfully, then redirects to /wp-admin/update-core.php?action=do-core-upgrade.

After that, I am getting an Error 500… and will redirect to /wp-admin/update-core.php?action=do-core-upgrade when trying to access any page under /wp-admin/. Like the OP, there is nothing showing up in the in the logs with my site either.

@chefjester
This is a slightly different problem from the OP as you have been able to install the update. This article here may help you manually delete W3: https://www.shoutmeloud.com/how-to-delete-uninstall-w3-total-cache-wordpress-plugin.html

@tjalexander70
If you haven’t already, go through the checklist, especially flushing your cache and deleting your cookies etc.

If that doesn’t solve things, it might help to delete the .htaccess file in the root of your website (make a backup first) and then regenerate it by visiting Settings -> Permalinks and hitting ‘Save Changes’. Sometimes a 500 error is caused by a corrupted .htaccess. Let me know if this solves the problem?

The issue is, we cannot get access to the dashboard to do anything.

@chefjester do you have access to your website files via FTP? It will be difficult/impossible to remove W3 manually without FTP access. If you do have FTP access, you can try following the steps laid out in the link I provided which do not require dashboard access.

I am in the process of trying, but not all the files it says to remove are listed… Ugh!

Hello,

I have same problem as described here. Whenever I start the update it stucks at the message “Downloading update from https://downloads.www.ads-software.com/release/wordpress-4.7-new-bundled.zip…”

So from there on nothing happens and I have to refresh the page.

SUCCESS!!!!!!! What a freaking nightmare! Thanks so much Alex!!!!

@hempsworth It seems the issues was not flushing the cache. I have everything up and running now. Thanks!!

• This reply was modified 7 years, 11 months ago by Tim.