-
Notifications
You must be signed in to change notification settings - Fork 401
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
Updating from GitHub adds an undesired suffix to the plugin folder name. #1
Comments
Another plugin that is similar to this, yet tailored for GH is https://github.com/jkudish/WordPress-GitHub-Plugin-Updater |
Thanks, @jaredatch 👍 |
@brasofilo I don't think there is a non-hacky way to accomplish that. The plugin suggested by @jaredatch uses a similar hack to rename the destination directory, except it relies on the "upgrader_post_install" filter instead of "upgrader_source_selection". |
@YahnisElsts , yep, discovered that two days ago... Thanks for the feedback! |
Renaming all of the clases and updating version numbers.
The notice: "Passing null to parameter #1 ($string) of type string is deprecated". This could be triggered because some update fields can be null, like the upgrade notice field.
If we use a GitHub zip file as
download_url
, e.g.,https://github.com/user/git-name/archive/master.zip
, the updated plugin receives an extra folder suffix:/wp-content/plugins/plugin-slug-master/
.I made a hack to deal with this, but wonder if there'd be a better alternative...
The text was updated successfully, but these errors were encountered: