#53990 closed enhancement (fixed)
Show a notice for incompatible plugins on the Plugins screen
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 5.9 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Plugins | Keywords: | has-patch has-screenshots needs-docs |
Focuses: | ui, administration | Cc: |
Description
In a discussion with @TacoVerdo we noticed that while a plugin incompatible with the installed WordPress or PHP version cannot be activated (as expected), the user experience could be improved.
Currently, incompatible plugins cannot be installed from the Plugin Directory as of [43436] / #43986, but if you happen to install such a plugin manually, there is nothing on the Plugins screen that would show its compatibility status. Clicking on the Activate link would just display a wp_die()
screen with an error message.
If a plugin does not work with the installed WordPress or PHP version, the Activate button should be disabled, and an appropriate notice should be displayed with a link to the documentation.
This is a follow-up to [43436] / #43986, [44978] / #43992, and similar changes for themes in #48491 and #48507.
Attached is a patch that handles this for the Plugins screen and the Add Plugins screen (disabling the Activate button for incompatible plugins that are already installed).
Attachments (8)
Change History (16)
This ticket was mentioned in Slack in #polyglots by tobifjellner. View the logs.
3 years ago
#3
@
3 years ago
53990.2.diff makes the icon consistent with the one for "There is a new version of ... available, but it doesn't work with your version of PHP" message.
#4
@
3 years ago
53990.3.diff also disables the Network Activate button on network admin Plugins screen.
#5
@
3 years ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from new to closed
In 51678:
53990.diff includes a new
.incompatible
CSS class for plugin rows to make sure the notice styling matches the one we have for plugin updates, see 53990.plugins-screen-after.png.53990.alt.diff just reuses the existing
.update
CSS class for that, which may or may not be cleaner. I don't have a strong preference yet at this point :)