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
Support for subdirectories #716
Comments
GHU wasn’t designed to use GitHub subdirectories. Much of the reason is how GitHub functions as GHU uses its native downloading the repository’s zip file. Much of the requirement means that the plugin’s base file be available in the root directory of the repo. If your plugin uses a build command you can use the release asset to add it to your GitHub repository’s release and GHU will use that for updating, but the root directory of your repo must contain a dummy main plugin file that is named identically to your main plugin file. This dummy file must have the updated version number as this is the file that GHU query’s for updates. https://github.com/afragen/github-updater/wiki/Settings#release-assets |
Added support for GitHub Updater Plugin Using release assets. See afragen/git-updater#716
Hi, thanks for your fast reply. And sorry for my late reply, didn't find time. I tried your solution with this plugin: https://github.com/jhotadhari/labeled-list-block Installed GHU and added personal access token. When updating, I get the positive green update-message notice that says: Labeled List Block updated!
Made another test and manually decreased the version number of the installed GHU plugin. Do you have any suggestions? Thanks a lot. Will reply faster this time ;) WordPress Version 5.0.1 |
The problem here is your release asset zip. It should have the following structure.
In other words the zipfile should unzip to a containing folder with the appropriate plugin slug and all plugin files go in that folder. This is a WP Core thing. |
https://github.com/cedaro/satispress also uses release assets. |
Fixed support for GitHub Updater Plugin with release assets Changed structure of release asset zip. Unzips to a containing folder with the appropriate plugin slug and all plugin files. See afragen/git-updater#716
Thanks a lot, |
Fixed support for GitHub Updater Plugin with release assets Changed structure of release asset zip. Unzips to a containing folder with the appropriate plugin slug and all plugin files. See afragen/git-updater#716
Hi,
does the updater work for plugins inside a repository subdirectory?
Why? My plugin repository is structured in source and distribution subdirectories.
For Example (I know GitHub Plugin URI declaration still missing):
This is not really an issue. Hope this is the right place for my question.
Thank you. If it works for my structure, I'll use it for all my projects.
The text was updated successfully, but these errors were encountered: