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
Bitbucket private repo Update error #482
Comments
Can you update from the update-core.php page? |
unfortunately, i tried and couldn't. This was the output i end up with
|
I think I found the problem. I switched to loading the Bitbucket authentication headers in the Update to 6.0.0.3 and let me know please. |
Weird, I can't see any notification of update for GitHub-updater plugin?! How I should upgrade to 6.0.0.3 also under your repo release, I can see only 6.0.0 version. |
Switch to branch |
My guess is the folder is misnamed. |
You might have read last comment of mine from #481. So, after unzipping new downloaded repo, i got github-updater-develop as name. Which didn't show me switch branch option. Even after renaming to github-updater, It was the same story. Unfortunately, About updating from bitbucket private repo, it didn't do the job from plugin panel but update worked from only update-core panel with disabling my plugin. |
Just so we have a new starting point. You have GHU v6.0.0.4 (develop) installed and running. In my test installation, I renamed my folder to What error are you getting when you attempt to update from the plugins page. Opening up your browser console error log should show you the errors. |
+1: I have the same issue after upgrading to the 4.x version. |
I cannot replicate this issue. Is it possible to give |
@afragen I applied your patch but this did not change anything. Unfortunately I cannot give you access to our BitBucket account. But if you need any logs let me know. Is there a simple way to downgrade? I already upgraded our staging and production environments. |
@cbratschi I don't need access to the whole account. I would just need Can you share the files headers? |
I'm having the same issue and can grant you access if you'd like to debug. |
Yes please. |
@afragen @yaronguez I grant you guys Read access. |
okay another update, i have installed new WordPress, downloaded and installed new GHU v6.0.0.4 (develop). This time didn't enable naming extend thing and clicked on enable branch switch and wrote my bit-bucket credentials. Lastly, clicked on private repo checkbox. Now after some refreshes, Switching branch option is being shown now. which is great 😸 |
@yeomann I found a bug, thanks. Update to 6.0.0.5 and let me know if you get the same error. Of course, it may not fix your issue, but possibly related. |
@yeomann I was able to remote install, revert version, and update successfully from plugin page, using v6.0.0.5 |
@afragen I tried to manually install 6.0.0.5 and got the error: I deactivated it and tried activating the clear-github-updater-cache.php file and then reactivated it and still get the error. The only version I can successfully activate is 6.0.0 which throws the zip error when I try to update a plugin. |
Can you install and activate the Flush cache plugin? |
Yes, I tried that. I had to deactivate github-updater to access the site at all since everything was white screen. Then I installed and activated the flush cache plugin. Then I deactivated the flush cache plugin and tried installing 6.0.5 again and again got the white screen. |
The error is because the cache isn't clear. Install but don't activate 6.0.0.5, activate the clear cache plugin, then activate GHU |
Do you have any caching enabled on your site? |
Yes, it's WP Engine and they have their own cache. What stage should I try to clear it? |
Okay, installing but not activating github-updater, installing and activating clear cache plugin, activating github-updater and clearing WP Engine cache seems to have fixed the problem. It also seems that I have to now clear WPEngine cache in order for plugin updates from BitBucket to be recognized. Is that expected? Thanks for all your help! |
I can't speak to how WP Engine's caching works but I would bet that it clears and refreshes more frequently than GHU's cache. I realize it's difficult to be patient but once you've satisfied yourself that everything works, give yourself 12 hours and see if the update shows. |
great work @afragen i'll check and tried to update shortly. Looking for returning with good news! Cheers. |
i was not able to update same error with v6.0.5 i think i will delete everything clear cache and start over to see, If i'll be able to update successfully (hopefully yes) or not. |
And... |
If I switch to the developer branch the updater tells me I am already at the latest version. |
It does that sometimes. Keep trying until it works. Shouldn't take too many tries. |
@afragen Still the same message after ten tries. It does not matter which branch I'm selecting. |
@cbratschi keep trying. It's the one thing I could never figure out how to override. |
@yeomann sorry for others hijacking the issue. Are you still having problems. |
@cbratschi I think I've fixed the already up to date issue 4dd351f |
@afragen Tried now many times but I was still not able to switch to the development version. When will you push the update to production? |
I should be pushing this out in next couple of days. Have you recently tried to switch? |
Another way to force a switch would be to edit the main file and set |
@afragen I've reset the cache and after that it was working. I could successfully update my theme after installing the development version. Thanks a lot. |
@yeomann are you still having this issue or should we close? |
I am sorry, but I have the same issue now with Bitbucket after using Bitbucket for a side project with a private repo. Update: |
@deckerweb I was able to install and update your plugin too. 👍 |
So, i have to confirm this, from #474 if you see my last message there, referenced comment
I did some digging and experiment. I have created new account on bitbucket and pushed my repo there and let it be Public. After filling bit bucket settings in github updater setting page, i saw notification of new update for my plugin and was able to update successfully my bitbucket hosted plugin with github-updater6.0.0. New version i.e 6.0.2 failed miserably #481
Now, after making the same Repo private i recived the same error mentioned in issue 474 and same error message as shown below in picture.
I now strongly believe my username and password in bitbucket settings of github-updater are correct and In case repo is private, github-updater is having trouble with bitbucket api. Please help.
Many thanks.
The text was updated successfully, but these errors were encountered: