Closed sc0ttkclark closed 3 years ago
I have had similar issues when installing the GitHub zip from release/2.8 directly onto the site, and a new update being made available on GitHub during the 2.8 beta. For instance, I had Pods 2.8 Beta 1 installed but Pods 2.8 Beta 2 was committed to GitHub and Git Updater wouldn't show that update available. To debug that at the time, I went to the plugin header and changed the version to 2.7.29 and it also only showed the 2.7.30 as available.
I had to downgrade to an older GHU version that had branch switching to see if manually doing the branch switch to main
and back to release/2.8
would resolve this but it doesn't totally. It only updates to that branch once, and future version updates still only show 2.7.30 (from .org) as the only valid option.
Hey Scott,
I'll take a deeper look at this when I get off work. Unfortunately work for the next few days is 7a to 10p.
Stay tuned.
Quick thought. You might need to use a filter to set the branch specifically to the site you're testing.
https://git-updater.com/knowledge-base/developer-hooks/
add_filter( 'gu_set_options',
function () {
return array(
'current_branch_pods=> 'release/2.8',
);
} );
To make Git Updater look to the release/2.8
branch for updates.
Let me know if this works.
Don't change the Primary Branch
header for the branch. It should always reflect the same data.
Reset back to Primary Branch: main
For our 2.8 RC testing folks, how do they get updates on the correct branch without using the branch switching Pro feature? In the past we used that primary branch to let people download the ZIP from GitHub and install. From there they would get updates.
If you can fix the Primary Branch header and add the filter to that branch, think that will work.
You won't be able to switch branches with the Git Updater PRO plugin but I think we can make it so your beta testers can update.
If you don't have Git Updater PRO, you won't be able to easily switch branches.
You might need to put that filter, correct for each branch, in each branch. Then deleting and installing a new branch should work. I'd need to test.
Have we fixed this?
We can close this for now, I'll open something up later if I figure find anything out of place. For now I'm using branch switching and that seems to be working good.
Pods has historically been set up for Git Updater but when testing with Pods 2.8 (beta and RC releases) it seems to have some sort of issue seeing the newer version from GitHub.
Plugin file with proper header: https://github.com/pods-framework/pods/blob/release/2.8/init.php
Specifically, the Git Updater plugin only sees the .org plugin version (2.7.30) and does not show (2.8.0-rc.1) as the newest version.
To get here, I first installed the .org plugin, changed the php header for the plugin file to point the primary branch to release/2.8, updated the plugin version to 2.7.29 so it will look for an update, and only then did I do a fresh install of Git Updater for the site I'm using (it was never on the site before).
This is a multisite network with Git Updater network-activated.
I am using my own personal auth key for GitHub to make sure that it wasn't that. I have bypass WP Cron turned on. I check and recheck the updates screen but it only shows the 2.8 RC version as expected.