Username:
TITLE
WordPress Toolkit: unable to restore a backup when table prefix is changed via Security Measures
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS Linux 7.9.2009 (Core)
Product Plesk Obsidian Version 18.0.41 Update #1
WordPress Toolkit
Version 5.9.3-6032
PROBLEM DESCRIPTION
When you start managing an existing WP website in WP Toolkit, you run into issues when you create a backup using the WP Toolkit and next apply the security measures like "Change default database table prefix".
If you want to restore the backup, it seems to be impossible:
"Failed to restore site from backup
"Note that changing database prefix on a website with production data might be dangerous, so it is strongly advised to back up your website before applying this measure."
STEPS TO REPRODUCE
- Scan for an existing WP website using the WP Toolkit (check if it uses the wp_ prefix in the database)
- Create a backup using the WP Toolkit
- Apply the security measure "Change default database table prefix"
- Try to restore the backup using the WP Toolkit
ACTUAL RESULT
You get an error and the website is broken:
"Failed to restore site from backup
EXPECTED RESULT
The expected result is that the backup is restored.
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
WordPress Toolkit: unable to restore a backup when table prefix is changed via Security Measures
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS Linux 7.9.2009 (Core)
Product Plesk Obsidian Version 18.0.41 Update #1
WordPress Toolkit
Version 5.9.3-6032
PROBLEM DESCRIPTION
When you start managing an existing WP website in WP Toolkit, you run into issues when you create a backup using the WP Toolkit and next apply the security measures like "Change default database table prefix".
If you want to restore the backup, it seems to be impossible:
"Failed to restore site from backup
- Error: The site you have requested is not installed.
- Your table prefix is 'wp_'. Found installation with table prefix: xxxxx_."
"Note that changing database prefix on a website with production data might be dangerous, so it is strongly advised to back up your website before applying this measure."
STEPS TO REPRODUCE
- Scan for an existing WP website using the WP Toolkit (check if it uses the wp_ prefix in the database)
- Create a backup using the WP Toolkit
- Apply the security measure "Change default database table prefix"
- Try to restore the backup using the WP Toolkit
ACTUAL RESULT
You get an error and the website is broken:
"Failed to restore site from backup
- Error: The site you have requested is not installed.
- Your table prefix is 'wp_'. Found installation with table prefix: xxxxx_."
EXPECTED RESULT
The expected result is that the backup is restored.
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug