Improve Incompatible Plugins Notice
Is your feature request related to a problem? Please describe. At the moment we show the same admin message for every incompatible plugin. In some cases, there could be another alternative besides deactivating the plugin, and/or we could provide a more informative notice.
Example case: Heartbeat Control plugin. This does not have to be deactivated if the Heartbeat feature in WP Rocket is disabled instead. We could provide that info in the notice which would be more intuitive and helpful for customers, and reduce the need to open a support ticket.
Describe the solution you'd like A way to provide additional context or information to the notice.
Describe alternatives you've considered n/a
Additional context Example tickets: https://secure.helpscout.net/conversation/2370615265/444753?folderId=377611 https://secure.helpscout.net/conversation/2352822186/441154#thread-7040577569 https://secure.helpscout.net/conversation/2276327572/425361/
This is not something that can be implemented in the nearest future.
https://secure.helpscout.net/conversation/2873371305/545496?viewId=377611
Since this list is now maintained in our backend, can we please add a new field that allows us to provide further information about the conflict? Example use case: https://github.com/wp-media/wp-rocket/issues/4997
Also, since 3.19 we show a conflict with the Custom Font plugin. We can include info that tells the customer to disable the preload option within that plugin to resolve the conflict:
- https://secure.helpscout.net/conversation/2968073584/566892
- https://secure.helpscout.net/conversation/2974000352/567986
This is also helpful for support to understand why conflicts have been added (in cases like Custom Font where it came during dev/QA and not from a support ticket)