WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#15177 closed defect (bug) (wontfix)

upgrading a plugin that doesn't exist

Reported by: jdingman Owned by:
Priority: normal Milestone:
Component: Upgrade/Install Version: 3.0
Severity: normal Keywords:
Cc: jdingman@…

Description

USE CASE:

  1. User is on the plugin upgrade page
  2. User deletes said plugin that requires upgrade via FTP or SSH
  3. User returns to the plugin upgrade page, clicks on "upgrade automatically" for said plugin

RESULT: screen prints.... "The plugin is at the latest version."

...it should probably say: "Plugin does not exist, please return to the plugin screen" or something like that.

Change History (4)

comment:1 dd323 years ago

  • Component changed from Plugins to Upgrade/Install

comment:2 ericmann3 years ago

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
  2. Updates said plug-in via FTP or SSH
  3. 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.

comment:3 dd322 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

comment:4 dd322 years ago

Based on it being an extreme edge case, and the final output is not "breaking" just displaying something unhelpful.

Note: See TracTickets for help on using tickets.