-
Notifications
You must be signed in to change notification settings - Fork 147
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
Some issues, and ideas #24
Comments
Agreed about the slug, I've got to dig into how WordPress generates the slug. I've had numerous occasions where the slug being different than expected caused problems. That's very interesting about blocking the the plugin from sending info over to WP.org as well. Yeah when the original script relied on a mysql database for securing the downloads I had thought about this as well. I currently mulling over moving this into a WordPress plugin to add some more advanced features. Just need the time. Thanks again for the report and ideas. |
to get the slug use i just release http://autohosted.com plugin to manage auto update. |
Just looked into plugin_basename, and when I was about to post, your message popped up. Good luck with the new plugin, why don't you make it into an optional service? |
@oferwald thanks. about service: no plan for that. you need to read this docs if you want proper sanitation for plugin sections: |
Looks like @turtlepod beat me to the plugin, good luck with that. I just haven't had time lately to work on this much, but I do plan on working on it again and hopefully fixing the problems that there might be. Like @turtlepod said a complete rewrite is in order and as of right now I just don't have the extra time. Hopefully soon though. |
@oferwald Hey! Could you elaborate on the upgrade_notice element? Where does that appear? I'm presuming that's what creates the highlighted band under a plugin with an update available? I'd like to be able to employ this as well. |
@holisticnetworking just add this to the packages array (if I remember correctly). |
bad use of slugs
the code uses the directory and then assumes that the plugin is in the format of slug/slug.php which is not always correct, sometimes the php file has a different name
missing upgrade_notice
Sending this can give a nice effect, and it just needs to be added to packages.php
a suggestion, stop querying wordpress.org when using internal updates.
Why inform and query wordpress.org on irrelevant stuff?
see this code example: (for example, to hide bbpress)
The text was updated successfully, but these errors were encountered: