Making WordPress.org

Opened 7 months ago

Closed 4 weeks ago

#7345 closed enhancement (wontfix)

Add "Compatible up to" plugin header

Reported by: azaozz's profile azaozz Owned by:
Milestone: Priority: normal
Component: Plugin Directory Keywords:
Cc:

Description

This idea has been floating around for a while. It would be really helpful for plugins to be able to set a maximum supported WP version in addition to the minimum/required version. That would allow the plugins to ensure they are being updated on time and will not cause errors in future versions of WordPress.

Thinking that an optional Compatible up to header in the plugin's file (same as Requires at least and Requires PHP) would serve that purpose well. Then in core that header can be checked and the plugin not loaded if WordPress is newer, similarly to how the Requires PHP check works.

On the plugins directory side the Compatible up to header may eventually be used to sent a warning message when installing plugins through wp-admin. Perhaps like "This plugin is too old and is not compatible with your version of WordPress" instead of the "This plugin has not been tested with your version of WordPress" when the header is present.

Change History (5)

#1 follow-up: @swissspidy
7 months ago

IMHO the cases this is useful for is limited to feature plugins and Gutenberg, and maybe a handful of other plugins that address things in a specific WordPress release. And all those plugins can just as well include some manual WordPress version checks.

#2 in reply to: ↑ 1 @azaozz
7 months ago

Replying to swissspidy:

the cases this is useful for is limited to feature plugins and Gutenberg, and maybe a handful of other plugins...

True. But still thinking Compatible up to should be handled by core even if it is only for feature plugins. Would make it easier for them and the plugins will not have to be activated in order to explain why they do not work and cannot be used.

This ticket was mentioned in Slack in #meta by courtneyengle. View the logs.


6 months ago

#4 @dd32
6 months ago

I personally think this is something that plugins should handle themselves, gracefully disabling themselves when they detect that the environment says they're no longer needed.

#5 @dd32
4 weeks ago

  • Resolution set to wontfix
  • Status changed from new to closed

Coming across this ticket again, I still feel the same, that this should be handled in code for the plugin, and/or core if it's significant enough.

A plugin could add the header, but the user experience would be better if they simply disabled themselves with a more descriptive error rather than just "Plugin XYZ has been disabled as it's not compatible with your version of WordPress".

Note: See TracTickets for help on using tickets.