Opened 7 years ago
Closed 7 years ago
#43952 closed defect (bug) (fixed)
Database error inserting cron job on fresh install
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.9.6 | Priority: | high |
Severity: | normal | Version: | |
Component: | Upgrade/Install | Keywords: | gdpr fixed-major |
Focuses: | Cc: |
Description
A database error occurs when installing a fresh copy of trunk
(and presumably the 4.9
branch).
WordPress database error: [Table 'wordpress_develop.wp_options' doesn't exist] INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('cron', 'a:2:{i:1525380534;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}s:7:\"version\";i:2;}', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)
Reported in Slack, props @helen for catching it.
wp_schedule_delete_old_privacy_export_files()
should be returning early during the install phase, but it's not. The bug was introduced in r43046.
Change History (3)
Note: See
TracTickets for help on using
tickets.
In 43162: