Hi @guilamu,
I found other topic like you here:
https://wordpress.org/support/topic/warning-xml-error-1-internal-error-huge-input-lookup-1/
I will post it here for your reference:
Hi @ya1112,
I think I have the solution to your issue. However, are you willing
to modify one line of code to see if it works? If not, you may grant us
temporary access to your system to make the change for you. If it works,
then we’ll include it as an option in future versions.
In backwpup/inc/class-jobtype-wpexp.php, line 411, you’ll see this:
$success = $dom->loadXML( file_get_contents( $job_object->steps_data[ $job_object->step_working ][‘wpexportfile’] ) );
Please change it to this:
$success = $dom->loadXML( file_get_contents( $job_object->steps_data[ $job_object->step_working ][‘wpexportfile’] ), LIBXML_PARSEHUGE );
Then please let us know if that works for you.
-
This reply was modified 8 years, 11 months ago by
happyAnt.
Hello,
I’ve made the change you requested and it did not changed a thing.
Exact same error.
Backups are also not properly working anymore: https://wordpress.org/support/topic/maximum-number-of-saved-no-longer-honired-diskspace-eaten-up/#post-9204192
Hi @guilamu,
If you restrict the XML export to only exporting a few content types, does it work?
As for the other issue, I’ve been posting the solution to that in a few different threads. Basically go to the job’s general tab, and hit save so that it regenerates the archive name. You will have to delete all old archives you do not want to keep.
@guilamu
were you able to solve your problem or do you still need help?
Kind regards,
Christina
Hello, thank you guys, the problem seems to be fixed.
Regards,
-
This reply was modified 8 years, 10 months ago by
guilamu.
Hi @guilamu,
Would you like to make us happy by giving us review and 5 stars rating?
That would help us make more features and more supports on free support forum, and especially, happier 🙂
If you want, you can make a rating here:
https://wordpress.org/support/plugin/backwpup/reviews/
