$scheduled_timestamp
$scheduled_timestamp : int
Timestamp equivalent of @see $this->scheduled_date
Class ActionScheduler_Abstract_RecurringSchedule
$scheduled_timestamp : int
Timestamp equivalent of @see $this->scheduled_date
$first_timestamp : int
Timestamp equivalent of @see $this->first_date
$recurrence : mixed
The recurrence between each time an action is run using this schedule.
Used to calculate the start date & time. Can be a number of seconds, in the case of ActionScheduler_IntervalSchedule, or a cron expression, as in the case of ActionScheduler_CronSchedule. Or something else.
$first_date : \DateTime
The date & time the first instance of this schedule was setup to run (which may not be this instance).
Schedule objects are attached to an action object. Each schedule stores the run date for that object as the start date - @see $this->start - and logic to calculate the next run date after that - @see $this->calculate_next(). The $first_date property also keeps a record of when the very first instance of this chain of schedules ran.
__construct(\DateTime $date, mixed $recurrence, \DateTime|null $first = null) : mixed
Construct.
| \DateTime | $date | The date & time to run the action. |
| mixed | $recurrence | The data used to determine the schedule's recurrence. |
| \DateTime|null | $first | (Optional) The date & time the first instance of this interval schedule ran. Default null, meaning this is the first instance. |
__wakeup() : mixed
Unserialize recurring schedules serialized/stored prior to AS 3.0.0
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. This was addressed in Action Scheduler 3.0.0, where properties and property names were aligned for better inheritance. To maintain backward compatibility with scheduled serialized and stored prior to 3.0, we need to correctly map the old property names.