serialized string error about search-replace-db

[elsonrodriguez]

Yep, this happened to me as well.

Version 2.2 works fine, but the current commit (129419a) does not properly re-serialize.

If anyone else is having this problem please use 2.2, the cli is not as fully featured as 3.0, but it works well:

https://github.com/interconnectit/Search-Replace-DB/tree/2.2.0

[roborourke]

Hi, sorry it's caused you problems. Very strange. I'll add some test cases
for the cli script. Can provide any additional info eg. PHP version etc?

[theDanielJLewis]

I know it's been a couple years, but any update on this? I just used the current version and it didn't serialize settings in my wp_postmeta table.

[zanzix]

Will be looking more into this soon

[adibpg]

Any news on this?

[theDanielJLewis]

At least for my needs, I discovered what happened with the some data in wp_postmeta. I posted details about this issue with WP-CLI's search-and-replace feature.

[lubieowoce]

just hit this :( Beaver Builder stores serialized PHP objects in wp_postmeta and certain string lengths weren't properly updated after changing the website url. the weird part is that it worked correctly in some cases, but failed in others (2 rows ok, 4 rows broken) with no obvious reason - the data is pretty similar in all 6 cases. they all contain UTF8 text, including 3-byte characters like em-dashes (the readme mentions them as problematic).

[roborourke]

@lubieowoce you could try changing the data in those 6 cases until it works successfully. Typically if the unserialisation fails it's because the object is not a stdClass and some other type of object that isn't loaded when the script is running. It's really unfortunate beaver builder stores custom objects in the database like this :/

[lubieowoce]

they are stdClass. however i just realized there's a chance that my issue isn't caused SRDB at all – i changed the url when restoring a Duplicator backup, so it might've gotten messed up back then (still weird that some of the posts were updated correctly). i'll make a fresh copy and try to eliminate that possibility