[wp-trac] [WordPress Trac] #15177: upgrading a plugin that doesn't exist
WordPress Trac
wp-trac at lists.automattic.com
Thu Oct 21 14:36:52 UTC 2010
#15177: upgrading a plugin that doesn't exist
-----------------------------+----------------------------------------------
Reporter: jdingman | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Upgrade/Install | Version: 3.0
Severity: normal | Keywords:
-----------------------------+----------------------------------------------
Comment(by ericmann):
This seems like an extreme fringe case - i.e. you'd have to 'try' to break
things in order to see this happen. Either way, the only issue here is
with the text of the message, not with what WordPress is actually doing.
If you've got your heart set on changing the message, though, you could
prototype a routine that verifies the plug-in exists after checking the
version. Right now, it looks like it's checking against the version
number stored in the database (lightweight, just a quick options lookup).
You could change it so that it loads the plug-in header instead and
verifies the version against that information - if the header loads, the
plug-in exists.
This would also prevent the (extreme fringe) case where someone:
1. Is on the plug-in upgrade page
1. Updates said plug-in via FTP or SSH
1. Returns to the upgrade page and clicks on "upgrade automatically"
The plug-in would already be up-to-date and wouldn't need an update ...
the system should alert the user accordingly.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/15177#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list