WP Toolkit Restore Issues

SPDTeam

• June 26, 2025 15:41
• Edited

Hi

I've experienced two issues recently with trying to restore a WP site from a backup created by WP Toolkit.

When I first tried running a restore it failed with an error saying something like "proc_open()` and/or `proc_close()` was not available". 

"proc_open" was one of the disabled PHP functions on the server. But I'm sure I've ran a restore in the past without it complaining about it, and I would have thought WP Toolkit would have its own php settings?

I removed proc_open from the server PHP.ini and tried again. This time it got past the original error but then complained with...

"wptoolkit" restore error Task failed ERROR 3730 (HY000) at line 1: Cannot drop table 'n5tFILvz_cli_cookie_scan_categories' referenced by a foreign key constraint 'n5tFILvz_cli_cookie_scan_cookies_ibfk_1' on table 'n5tFILvz_cli_cookie_scan_cookies'. [error]FailedToExecuteWpCliCommand: exit status 1[/error]

For reference when I started the restore the "Delete existing data before restoring" was enabled.

Disabling this option allows me to restore, although I'd assume the DB will contain erroneous entries.

Anything I'm doing wrong?

• 

  William Del Piero cPanel Staff

  • June 26, 2025 17:52

  Hi,

   

  Regarding the "proc_open/proc_closed not available" issue, it's possible this function was needed by the WordPress installation from a custom theme or plugin. If you haven't already, I suggest checking the WP Toolkit error logs to see if any further detail is given regarding these errors, as sometimes that can help highlight the root cause of the issue. I'll include articles below with details on enabling enhanced logging and another with the log locations for WP Toolkit:

   

  How to troubleshoot WP Toolkit

   

  How to enable Enhanced Logging in WP Toolkit

   

  Regarding the database error, it appears that there is an issue with removing the n5tFILvz_cli_cookie_scan_categories table. As such, you will likely need to manually remove this table so the database can be fully removed. One option for this would be to run a drop query for this table in PHPMyAdmin with the option to "Enable foreign key checks" unchecked. I was able to find some additional discussion on this topic that may prove useful:

   

  Can't drop table a foreign key constraint fails

   

  If you haven't already, I suggest ensuring you have a backup of this database before performing any changes to minimize the risk of data loss.

  0

Please sign in to leave a comment.