`wp_get_schedule()` not supported, causes issues with Jetpack 4.4 about cavalcade HOT 5 CLOSED

I've started adding a proper schedule field in https://github.com/dd32/Cavalcade/tree/add-schedule-support

It still needs an upgrade routine, and probably the ability for the plugin to operate on an out-of-date table (unless manually upgrading tables prior to upgrading the plugin is an option).

from cavalcade.

We've hit into this as well. @dd32 Is your branch ready for a pull request?

from cavalcade.

@rmccue I've been using it locally (not on W.org) successfully without issue (With Jetpack).

It lacks any form of upgrade routine to add the column to the database, and will probably explode if activated on a older schema.
Other than that, it should be ready to go, shall I PR it in it's current state?

from cavalcade.

Better to file the PR early. :)

As to how we handle upgrades, I'd add detection for the column and use it if we can, trying to avoid errors if possible. We can potentially store a version in network options if needed for performance. The actual upgrade itself I think is best on a CLI command, and we can add a trigger_error( ..., E_USER_NOTICE ) if the version is out of date.

from cavalcade.

A schedule column was added in #62.

from cavalcade.