UPDATE — severity raised. After deleting the staging clone via the WP Staging
UI (clone “cerritos”, same database, prefix wpstg0_), ALL tables of our
PRODUCTION site (prefix wp_) were emptied row by row about an hour later —
the tables still existed but had 0 rows, only the largest table still had
data, and the site showed the WordPress installer (wp_options empty). The DB
user had no DROP privilege at the time, which is presumably why the tables
were emptied instead of dropped. We restored from a backup and have removed
WP Staging from the site. Please investigate why the delete job targeted the
production prefix. The fatal error in Frontend.php from my first message
occurred on the same clone right before.
I will not go any further with WP Staging, have disabled the plugin and use my hosts Staging solution
