I understand this is resolved, but wanted to chime in with my two cents anyway.
I have been using MainWP Child for 6+ months on my client’s website. They have a fairly busy ecommerce website with plenty of public and admin traffic.
I was just pulling my hair out about during a database migration because the wp_options
table kept failing to import. I traced it down to a single row. The problematic row had an option_name
of mainwp_child_subpages
and a value over 120 million characters in length.
After browsing through MainWP Child’s code, it seems this option is unused in the current version. Excluding this row from my import allowed the import to proceed unhindered.
Not too sure what this would have been used for, or how it grew to such a size, but my oh my did this ever give me a headache.
-
This reply was modified 4 years, 3 months ago by pixelbrad.
-
This reply was modified 4 years, 3 months ago by pixelbrad.