Greetings:
It seems that I am not the only person that has challenges using WF with Duplicator.
The Duplicator error I receive when scanning to make a package is
**********
Overview:
The thresholds that trigger warnings for individual tables are 10MB OR 100,000 records OR tables names with upper-case characters. The larger the table the more time it takes to process and execute. This can cause issues with budget hosts that have cpu/memory limits, and timeout constraints.
Options:
1. Run a Repair and Optimization on the table to improve the overall size and performance.
2. Remove stale date from tables such as logging, statistical or other non-critical data.
3. For table name case sensitivity issues either rename the table with lower case characters or be pre-paired to work with the lower_case_table_names system variable setting.
**********
I found the following WF tables associated with the error:
wp_wfBadLeechers
Case:1
Rows:0
Size:16KB
wp_wfBlockedIPLog
Case:1
Rows:0
Size:16KB
wp_wfBlocks
Case:1
Rows:0
Size:32KB
wp_wfBlocksAdv
Case:1
Rows:0
Size:16KB
wp_wfConfig
Case:1
Rows:131
Size:16KB
wp_wfCrawlers
Case:1
Rows:16
Size:16KB
wp_wfFileMods
Case:1
Rows:5,332
Size:1.52MB
wp_wfHits
Case:1
Rows:1,699
Size:1.22MB
wp_wfHoover
Case:1
Rows:212,051
Size:39.08MB
wp_wfIssues
Case:1
Rows:0
Size:16KB
wp_wfLeechers
Case:1
Rows:1,214
Size:112KB
wp_wfLockedOut
Case:1
Rows:0
Size:16KB
wp_wfLocs
Case:1
Rows:0
Size:16KB
wp_wfLogins
Case:1
Rows:31
Size:48KB
wp_wfNet404s
Case:1
Rows:0
Size:32KB
wp_wfReverseCache
Case:1
Rows:0
Size:16KB
wp_wfScanners
Case:1
Rows:0
Size:16KB
wp_wfStatus
Case:1
Rows:980
Size:256KB
wp_wfThrottleLog
Case:1
Rows:0
Size:32KB
wp_wfVulnScanners
Case:1
Rows:0
Size:16KB
What suggestions do you have other than removing WF before running Duplicator? Is there a fix coming soon?
Thanks!
fred
https://www.tech-wise.services