Opened 4 months ago
Last modified 7 weeks ago
#23318 new enhancement
Plugins Admin Showing Details for Wrong Plugin
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | WordPress.org |
| Component: | Plugins | Version: | |
| Severity: | normal | Keywords: | 2nd-opinion |
| Cc: | crazycoders |
Description
I just set up a new site with some plugins, none of them activated yet. The plugins screen says:
"There is a new version of Google XML Sitemaps available. View version 4.1 details or update now."
I know for a fact there is no such version of this plugin. When I click details link, it tells me to install some other plugin called page-list?!
Change History (4)
comment:1
miqrogroove — 4 months ago
comment:2
SergeyBiryukov — 4 months ago
- Milestone changed from Awaiting Review to WordPress.org
- Version 3.5.1 deleted
+1, this needs a smarter mechanism IMO. In my code, I use an extra plugin header called Plugin ID: xxx, where xxx is the slug on the repository. We could add something like that, with a legacy fallback to the directory name (and eventually mark that as deprecated).
comment:4
crazycoders — 7 weeks ago
- Cc crazycoders added
- Keywords 2nd-opinion added
- Severity changed from critical to normal
- Type changed from defect (bug) to enhancement
Agreed with the smarter mechanism but this is kind of a stupid bug.
Renaming the folder of a plugin willingly and it calling it a bug because it shows the patch for another plugin thats kinda like saying "I busted my car engine cause i used normal grade gas while i was supposed to use super grade but it's not my fault, it's the maker's fault for not letting me do it"
I don't think this should be kept open as the changes that are required to end up making this work would be really broad and could introduce many other bugs. Or if it must stay open, then it should be marked as an enhancement for a future release instead.

Steps to reproduce:
Using the directory name to detect plugins seems like a bad design!