Release v3.2.3 · renatobo/eventon-apify

New Features

EventON is named as a dependency on the admin side. Every endpoint already failed closed when EventON was absent, but it failed closed with a 500 that only an API client ever saw, and the settings screen said so only if you opened it. An admin notice now reports a missing EventON on any admin screen, so the cause is visible from the dashboard rather than from a response body.
The notice reads the same eventon_apify_is_eventon_available() the routes use, rather than defining a second idea of "EventON is here" that could drift from what the test suite pins.

The dependency is declared at runtime rather than through the Requires Plugins plugin header. EventON installs into a directory named eventON, and WordPress drops any dependency slug that is not lowercase-and-hyphens, so it can never be named there. The runtime check also catches EventON being deactivated after this plugin was already running, which the header does not.