WPIntell

Source evidence

Method 1

Backup Migration · support · 2026-07-02T20:17:00+00:00

complaintsentiment
highseverity
0.78relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 25 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

20 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
vilo1968 unresolved
Hi again, I performed some additional testing on a public website (not an intranet), and I found another issue that seems to be related to Method 1 . Here are the results: The website is publicly accessible. It uses Wordfence . Initially, Wordfence reported a false positive for one of the Backup Migration AJAX requests. I accepted the suggested allowlist rule. I tried creating another manual backup using Method 1 , but it failed again. To completely rule out Wordfence, I disabled the Wordfence plugin and tested Method 1 again. It still failed. Then I switched Backup Migration to Method 2 , and the manual backup completed successfully. I also reviewed the generated log and found something interesting. The backup process actually starts and later reports: “Backup file created successfully via backup-process.php” However, during Method 1 the frontend AJAX request receives a 404 response containing the full HTML of the website’s 404 page , instead of the expected AJAX response. After that, several AJAX requests report “NetworkError”. This makes me think that the backup itself is actually being created, but the frontend reports it as failed because one of the AJAX requests unexpectedly returns a 404 page. Could you please check whether this is a known issue with Method 1? Debuge code: BMI-4BSCbO48-72012 Thank you!

Comments

0 shown

No comments were stored for this source.