-
-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update failed #481
Comments
This may be related to #482 |
Is there some reason you're using the extended naming? It's really there only to avoid slug conflicts with the .org repo. |
The above error is due to the new optimize transients. Using the branch switch to jump between branches should automatically refresh the cache. This is the error you see. How were you changing from master to develop? |
If this or similar error returns I wrote a one off plugin to fix it. |
i was just testing with it.
Can't see still this option, even downloaded new repo from github. After unzipping downloaded zip, Folder name was github-updater-develop. With that no switch branch option came up. Even i renamed to github-updater and same no branch switch option. So, Here's what happened. I downloaded new github-updater from repo with version 6.0.0.4. upon first activation it throws error and made my plugin panel inaccessible. See picture for that below. After using your clear Transients above mentioned plugin. It did the trick and i was able to activate github-updater plugin successfully. It also detected update changes for my private bitbucket repo and did Update only from update-core not from plugin panel but after updating, It disabled my plugin. I will close this issue so we can follow up at issue #482 |
i tried to update to new version 6.0.2 from 6.0.0 and got this error. See picture as well for what happen afterwards.
Update Failed: Rename successful using extended name to github-afragen-github-updater…
edit: i can't enable github-updater plugin now. i tried to rename from ftp and then tried to enable it from wp admin. but it pops the same error like above picture. i'm going to download now 6.0.0 release from GitHub and hope everything will be fine.
edit: so yeah github-updater 6.0.0 is working fine.
The text was updated successfully, but these errors were encountered: