Plugin Contributor
Matthew
(@kidsguide)
The reason why it is names “stops-core-theme-and-plugin-updates” is because when the plugin was first made (two years ago) that was the name of it. Now of course we have expanded the plugin and turn it into a full updates manager. The only problem is that WordPress keeps the original plugin name for the name on the plugin directory. So it is not possible to change that. That’s why you will also see in the URL for the plugin the “stops-core-theme-and-plugin-updates” (https://ww.wp.xz.cn/plugins/stops-core-theme-and-plugin-updates/).
As for changing the main.php to easy-updates-manager.php we should have done that a while ago. I will talk to the others about changing that in the upcoming versions.
This is not our fault. We inherited this plugin and its install/user base.
WordPress stores activated plugin as slug/filename.php.
We’re unable to change both.
Thread Starter
gwc_wd
(@gwc_wd)
I sincerely thank you for taking the time to explain things to me.
Perhaps the Repository Gods will take pity and relent on what seems an unnecessarily strict adherence to such a policy.
So my frustration is transformed into gratitude that you stepped up to maintain the project! I knew none of that history. Perhaps a note in the readme.txt would help such as (formerly known as Stops-Core-Theme-And-Plugin-Updates).
Anyway, sincerely thank you for both doing the actual work and in explaining the backstory.
Sorry, just saw this reply. I re-read my reply and it seemed terse. Sorry about that.
When you (you as in general) add a plugin to the WordPress repo, it requires a bit of forward thinking. Name the plugin as well as you can, and hope the stars aline.
Sometimes, as with this plugin, it evolved to include a more in-depth feature set.
Matthew and I talked in-depth before releasing the major 5.0 update about possibly just creating a new repo.
The benefit of using this same plugin was it already had an established user base (10000+ install at the time) and had already evolved into providing granular control over plugins/themes.
As far as repo gods changing the slug, the plugin team has repeatedly told me this is basically impossible.
1. It’s the way WordPress stores its activated plugin settings (slug/filename).
2. Changing the slug here on the repo would break/discontinue/abandon users who had the old slug installed.
3. A recent reason is language packs. Each slug on .org has to be unique in order for those to work, otherwise you run into naming collisions, and I imagine it makes it significantly easier to program knowing a translation matches a unique and unchangeable slug.
As I stated, ideally we get the slug right the first time. It doesn’t always work out. A very popular example is WordPress SEO by Yoast, which is now Yoast SEO. The slug remains. https://ww.wp.xz.cn/plugins/wordpress-seo/
Take care and have a good weekend should this find you!
To put this issue to bed so-to-speak, and we almost did this ourselves… this is what happens when you change the main plugin file name.
http://www.zdnet.com/article/my-open-source-wordpress-plug-in-lessons-learned-from-a-release-gone-wrong/
