esleight
Forum Replies Created
-
Activating it first seems to work! I did it on our staging server and it looks good. Thanks so much for the advice!
Thanks for getting back to me. I can try to reinstall a little later. I did download the most recent version of the plugin and I still see the “priority” column references in the code… if it helps this is where it is being set:
$data = array(
‘hook’ => $action->get_hook(),
‘status’ => ( $action->is_finished() ? self::STATUS_COMPLETE : self::STATUS_PENDING ),
‘scheduled_date_gmt’ => $this->get_scheduled_date_string( $action, $date ),
‘scheduled_date_local’ => $this->get_scheduled_date_string_local( $action, $date ),
‘schedule’ => serialize( $action->get_schedule() ), // phpcs:ignore WordPress.PHP.DiscouragedPHPFunctions.serialize_serialize
‘group_id’ => current( $this->get_group_ids( $action->get_group() ) ),
‘priority’ => $action->get_priority(),
);
And this is where it blows up on me:$insert_sql = $this->build_insert_sql( $data, $unique );
I’ll try to reinstall later after hours.
Thanks!!The column does not exist currently. I’m not sure if it existed in the past, but it doesn’t exist in the current version that we have (6.2.2). In order to be able to activate the plug-in, I added a line of code to the one of the plug-in PHP files (ActionScheduler_DBStore.php). It simply removes that column prior to the INSERT INTO call to the the database. I’m not sure why it would be trying to write to a column that doesn’t exist. This particular column (‘priority’) is mentioned in several places in the code. Maybe it was deprecated?