ianmjones / wp-cron-pixie Goto Github PK

I think not, and it would be great to get rid of npm and yarn as dependencies so we don't have to deal with the security updates for stuff we don't even use in the plugin itself.

All we need is Elm for compiling, which is easily installed on any platform without the need for npm these days (although still an option if you prefer it for some reason).

Currently the cron_pixie_passed_event, cron_pixie_future_event and crop_pixie_single_event cron events are created as examples of how events are shown.

These should be optional, and only shown when the user asks for them.

At the moment a bunch of text in the UI is not translatable as it is text strings in the Elm code.

The text should come through from the PHP code on initialization.

At present WP Cron Pixie continuously checks and displays the current cron events every 5 seconds, it should be possible to pause automatic refresh.

The initial fetch of data displays the correct cron events for the current subsite, but when the dashboard widget fetches new data it receives the primary site's cron events.

Given that issue #3 get implemented, there should be a mechanism for the user to refresh the display as and when they require it rather than have to turn automatic refresh back on.