Skip to content

Run Now often causes error #97

@robgilde

Description

@robgilde

Found in 1.5.2.
Possibly related to Issue #33.
I stepped through this in a debugger and I think I've identified the root cause.

force_schedule_single_event() calls _set_cron_array()
_set_cron_array() calls update_option()
update_option() returns "true if the value was updated, false otherwise". False is not necessarily an error condition - it can be false if the save was unnecessary.
However, the false result is propagated back up and force_schedule_single_event() at line 108 treats it as an error.
I think line 108 should be something like if ( $wp_error && ! $result ) {

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions