53b5112ca2
r43046 introduced `wp_schedule_delete_old_privacy_export_files()` to schedule the `wp_privacy_delete_old_export_files` cron job, but it did not check to make sure it wasn't running in the context of the install process. When it did run in that context, it created a database error, because the necessary database tables don't exist at that point. Checking the current context and returning early during the installation phase avoids that issue. Props helen, timothyblynjacobs, iandunn. Fixes #43952. git-svn-id: https://develop.svn.wordpress.org/trunk@43162 602fd350-edb4-49c9-b593-d223f7449a82 |
||
|---|---|---|
| src | ||
| tests | ||
| tools/i18n | ||
| .editorconfig | ||
| .gitignore | ||
| .jshintrc | ||
| .travis.yml | ||
| composer.json | ||
| composer.lock | ||
| Gruntfile.js | ||
| jsdoc.conf.json | ||
| package.json | ||
| phpcs.xml.dist | ||
| phpunit.xml.dist | ||
| webpack.config.dev.js | ||
| webpack.config.prod.js | ||
| wp-cli.yml | ||
| wp-config-sample.php | ||
| wp-tests-config-sample.php | ||