Undefined class constant 'CATEGORY_NOTIFICATIONS' about notify-plugin

[stelgenhof]

@LukeTowers Thanks for the update! Next time I will indeed checkout the documentation of plugins :)

In this case, the plugin was causing much harm in the sense that October didn't work anymore. Many users might not immediately checkout the marketplace documentation, so a warning of some sorts in the UI could help users understand about the risk of installing plugins.

Just a nice to have; understand if it's not a priority at the moment.

Cheers! Sacha

[daftspunk]

This plugin is only compatible with Build 420+

[stelgenhof]

I experienced exactly the same. Understand that it is only compatible with Build 420+ but how do I recover from this? Don't want to reinstall OctoberCMS again preferably.

[LukeTowers]

@stelgenhof do you mean make your October instance work again without this plugin or do you mean make it work with this plugin?

[stelgenhof]

@LukeTowers Well, this error appears all the time in the backend so the backend is unusable. In the end I removed the notify plugin files from the plugin folder. That way the backend worked again.

It may be better if plugins that are in beta or for a specific build be marked as such in the UI for example. Just to avoid people experiencing similar issues in the future :)

[LukeTowers]

To be fair it says it clearly at the top of the readme and on the marketplace. If you have an idea for a specific UI enhancement I'd be welcome to hearing it, but typically we're unwilling to support users of plugins that are unwilling to upgrade to the latest version of October, especially given the amount of work we put in to make sure October base upgrades are as hassle-free as possible for the user.

Granted 420 is a special case with the switch the Laravel 5.5 and PHP 7, but there aren't really very many good reasons for still using a version of PHP < 7.