Hi Toolset Team,
Today it's the second time my website go down during an update with Toolset and apparently specially during the update of CRED. Once if I'm right with the 1.9.2 then today with 1.9.3
Before suggesting the improvement, I would like to share and to describe what was my problem an how I've (apparently) fixed it.
So, on a sandbox website (online) that is the exact copy of my production site (Worpdress 4.8.3, Toolset, Divi, W3Total Cache and Yoast), the first time my website went down because :
1 - In Dashboard, I was invited to update the Toolset plugins, about 2 or maybe 3 weeks ago), I selected all and press the update button, then I get the Fatal error message, I was unable in any way to solve this problem but with a previous Duplicator backup uploaded by FTP on my sandbox.
2- Then with this fresh copy I selected one Toolset plugin and press the update button with no problem, then I pass to the next one with no problem, ... until I updated CRED. I got the Fatal error.
3 - I then manually updated CRED passing by the FTP and your download page
--> Problem solved
--> I did on my production website the update one by one process into the Dashboard with no problem and no need to go with FTP.
So I move on.
Today with your latest update, my website went down even if I did :
1 - Update plugins one by one into the Dashboard of my sandbox with NO PROBLEM
2 - Update plugins one by one with my prod website, I've got the Fatal error while updating CRED (Fatal error require_once(): - '/class.cred.php')
3 - Updating CRED using the FTP - No effect
4 - Removing directory on the FTP and copy my previous backuped directory of CRED - No effect
5 - Removing all the Toolset directories and copy the new one from your download page
--> Problem solved
I've to say here that I've managed the cache plugin and purged when needed to be sure it wasn't related to.
So here is my question and maybe could it become an improvement suggestion :
Apparently the Fatal error appears randomly or is related to the order into which we update your plugins, but always with CRED ! Is it possible ?
If it is, could it be possible to not allow to update Toolset plugin by plugin, but all in a row ?
Doesn't matter if there is an update for Types and CRED or for Types, CRED and Views or any kind of other combination, we click once to update and your "installer" manage the rest !
I'm not sure if I explain in the right way and it could help, but in any case do not hesitate to contact me I you eventually need further details.
Wishing you the best !
Julien
Hi, sorry you're having trouble updating Toolset plugins. When the missing class.cred.php file error appears, this typically indicates a download problem during the automatic update process for a plugin, and could be related to either Views or CRED. For best results, disable your cache plugin before the updates, then reactivate and purge cache after the updates are complete. If you're updating several plugins at the same time (either automatically or with FTP) I generally recommend the following order:
<ol>
Types
Views
Layouts
CRED
Access
Any other Toolset plugins
</ol>
2 - Update plugins one by one with my prod website, I've got the Fatal error while updating CRED (Fatal error require_once(): - '/class.cred.php')
5 - Removing all the Toolset directories and copy the new one from your download page
--> Problem solved
This seems to indicate the problem was actually in Views, since simply updating CRED was not enough to resolve the issue. My guess is that the Views automatic update encountered a problem, or CRED was updated before Views and an older version of Views was already active.
Hello Christian,
thank you for your list, my logic was the opposite as I started with CRED, Layouts,..., I will try during the next update your order and I will prefer the FTP way.
What about the idea to make an "update all" button managed by Toolset to avoid any issue ?
Again thank you.
Julien
The "Update all" button sounds like an idea that could be submitted as an improvement to Toolset, we also call those feature requests. They're handled a bit differently than how-to or bug tickets, so may I kindly ask you to start a new "improvement" ticket that includes this information? Our team will analyze the proposal and let you know our decision to accept or reject it. Thanks!