I am trying to: reopen ticket https://toolset.com/forums/topic/cant-update-the-plugins-without-getting-an-error/#post-1207189
Link to a page where the issue can be seen: Removed, rolled back via VaultPress because of catastrophic error.
I expected to see: Plugin update completed normally, no issues
Instead, I got: Catastrophic failure, plugin failed to complete. I tried updating manually, same problem. I ended up having to roll back to last valid site via VaultPress.
So I went looking for anyone else who had the issue and saw ticket #1207189. The last commenter said there were case issues (differences in case of directories):
>>>
We where facing the same issue and where able to solve it. The issue was a change in case of a folder name. On case sensitive file systems this throwed this error.
If you deploy your code through GIT make sure to disable git's ignore cases setting, you will see that the following folder has changed cases and was not found by git.
After upgrading:
wp-content/plugins/type-access/vendor/toolset/toolset-common/inc/autoload/upgrade/Command
Before upgrading:
wp-content/plugins/type-access/vendor/toolset/toolset-common/inc/autoload/upgrade/command
February 27, 2019 at 4:35 pm #1207189
<<<
I checked the release notes, no mention of case changes in any recent release. Nor was there any mention that the case issues had been addressed or fixed in later releases.
I'm now stuck and cannot upgrade.
Will you be fixing this issue? Are you verifying no case conflicts?
Hello,
As you can see:
After upgrading, the folder name is "Command",
Before upgrading, the folder name is "command",
The folder name has been changed.
And we have already some similar reports, for example:
https://toolset.com/forums/topic/change-in-case-of-command-folder-broke-my-sites/
Here is the feedback from our developers:
Our whole development process is case-sensitive and if the clients wants to deploy Toolset plugins in another way than through the standard WordPress plugin upgrade mechanism, they need to make sure the case-sensitivity is not a problem in the deployment. Personally, I would suggest to adjust the deploy script so that the plugin directory is first deleted/completely emptied and then the plugin is downloaded again.
So you will need to make sure case-sensitivity is not a problem in the deployment yourself.
It was recommended that you adjust the deploy script so that the plugin directory is first deleted/completely emptied and then the plugin is downloaded again.
If you have "Access" plugin file managed by git, you might choose to do something like this:
cd types-access
# delete all files and directories except dotfiles, so the .git directory is preserved
rm -rf *
git reset --hard origin/master
It's not an issue with the standard WordPress update mechanism as that's exactly what I was using when it failed. If not the case sensitivity issue, why is it failing to update through the standard process?
I assume we are talking about "Toolset Access" plugin。
I have tried it in my localhost in a fresh wordpress installation, upgrade the Access plugin from 2.6.1 to 2.6.2 using standard Toolset upgrade process:
https://toolset.com/faq/how-to-install-and-register-toolset/#automatic-installation-once-you-have-types-plugin-installed
See screenshot: access-upgrade.JPG.
It works fine, there isn't the problem you mentioned above.
Please try this:
1) Make sure you are using the latest version of Toolset Types plugin.
2) Deactivate other plugins (), and switch to wordpress default theme 2019
2) Go to Plugins -> Add new and click on the Commercial tab.
Follow above document to upgrade Access plugin, and test again
I've been using Toolset since December 2017 and no update has failed _until this most recent one_.
My issue isn't related to a fresh install, so I'm not sure how that information (your test) helps here.
I tried using the update ... BUT I GET AN ERROR EVERY TIME
Thanks for the details, in your screenshot:
hidden link
There is a error message:
...PCLZIP _ERR_BAD_FORMAT...
This is a known issue of old version of Types plugin, since the Toolset Installer featured is embedded in the Types plugin, so if you are using old version of Types plugin, and upgrade other Toolset plugins, it will conduct the problem as your screenshot.
Please try this:
Upgrade Types plugin manually:
Dashboard-> Plugins-> Deactivate/Delete "Toolset Types" plugin
Install the latest version of Types plugin manually, you can download it here:
https://toolset.com/account/downloads/
And test again.
