Closed jefrey1f closed 3 years ago
I'm having the same issue. Reverting to 3.1.0 succeeds.
We are also getting a similar issue. When we tried the CLI version we got the issue mentioned in #348.
I ran 3.1 on the CLI and it worked perfectly. The debug command didn't shed any light on the exact string that was failing.
the 3.1 has a more bare bone replacement system, the version 4.x is more careful in changing the database. Some plugins like to serialise classes and weird data in wp_options and you cannot predict what's inside for a search/replace operation. Another tool like wp-cli can avoid this but it loads the entire wordpress app in memory for the operation, try that :)
3.1.0 passes on Yoast SEO's serialized classes too, so it seems safe to stick with 3.1.0 for the time being. Thank you for all your hard work.
4.1.2 fails on one specific table (attached) but reverting to v3.1.0 works just fine. The error alert is:
I've attached an export of the failing table. I have renamed the table for testing purposes (this was the wp_usermeta table) and randomized some user data (while maintaining serialization lengths) but otherwise have not modified the table. Any advice is appreciated. Thanks -jeff
wp_jlrtest.zip