Description #Description

Prior to Action Scheduler 3.0.0, schedules used different property names to refer to equivalent data. For example, ActionScheduler_IntervalSchedule::start_timestamp was the same as ActionScheduler_SimpleSchedule::timestamp. Action Scheduler 3.0.0 aligned properties and property names for better inheritance. To guard against the scheduled date for single actions always being seen as "now" if downgrading to Action Scheduler < 3.0.0, we need to also store the data with the old property names so if it’s unserialized in AS < 3.0, the schedule doesn’t end up with a null recurrence.