unserialize(): Error at offset 203 of 1226 bytes

Question

unserialize(): Error at offset 203 of 1226 bytes

sebastienserre opened this issue 8 years ago · comments

Sébastien SERRE commented 8 years ago

Hello,

I'm using your tool on my localhost and have this error:
"unserialize(): Error at offset 203 of 1226 bytes"

ddo you know what's happen?

arnolito commented 8 years ago

Idem

Thierry Pigot · Answer 1 · Mon Oct 17 2016 15:47:19 GMT+0800 (China Standard Time)

I have the same problem :(

iouston · Answer 2 · Thu Oct 20 2016 20:55:10 GMT+0800 (China Standard Time)

And me too

NetAgence · Answer 3 · Sun Feb 05 2017 23:13:45 GMT+0800 (China Standard Time)

Same here, interested in getting updates. In case it helps, result was:

Results
RESULT occurence(s) found and replaced.
Restart
unserialize(): Error at offset 554 of 579 bytes

Migration test done on an up-to-date Linux CPanel server, PHP 5.6.

Edit: after using a "competition" tool that-shall-remain-nameless, I got:

2: Insufficient data for unserializing - 514 required, 503 present in /my-domain-path/Search-Replace-DB-master/srdb.class.php on line 735
2: Insufficient data for unserializing - 1878 required, 1843 present in /my-domain-path/Search-Replace-DB-master/srdb.class.php on line 735
2: Insufficient data for unserializing - 480 required, 477 present in /my-domain-path/Search-Replace-DB-master/srdb.class.php on line 735
2: Insufficient data for unserializing - 2232 required, 2169 present in /my-domain-path/Search-Replace-DB-master/srdb.class.php on line 735

even though the replace worked with it.
Could that be linked ?

Thanks.

Daniël van de Giessen · Answer 4 · Tue Feb 14 2017 21:24:10 GMT+0800 (China Standard Time)

I've finally had some time to look into it. The initial problem turned out to be the regexes which handle broken serialized data did not properly supporting namespace in the serialized object name. Resolved that and am no longer able to reproduce the error, thus closing this issue. Fixes are available in v2.1.1. If you still have problems, let me know. :)

Fabien LEGE · Answer 5 · Mon Oct 19 2020 18:54:16 GMT+0800 (China Standard Time)

Always the same problem with extended search ...

Daniël van de Giessen · Answer 6 · Mon Oct 19 2020 19:03:01 GMT+0800 (China Standard Time)

Hi @fabienlege!

What are you using extended search for, are you running search-and-replace on some special serialized values?

Which version of PHP are you running and can you perhaps share the full error message and/or an example I can use to reproduce the issue? Thanks!

Fabien LEGE · Answer 7 · Mon Oct 19 2020 19:06:32 GMT+0800 (China Standard Time)

I use extended search to migrate wordpress website. I exécute a search and replace to replace domain name in database Le lun. 19 oct. 2020 à 13:03, Daniël van de Giessen < notifications@github.com> a écrit :

…

Hi @fabienlege <https://github.com/fabienlege>! What are you using extended search for, are you running search-and-replace on some special serialized values? Which version of PHP are you running and can you perhaps share the full error message and/or an example I can use to reproduce the issue? Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPTO5WU5BSVGRZYLARMFYTSLQMHPANCNFSM4CQG4HPA> .

Daniël van de Giessen · Answer 8 · Mon Oct 19 2020 19:25:11 GMT+0800 (China Standard Time)

When replacing a domain name in Wordpress, you probably don't need to use the "extended search" option. DBSR is a lot faster without it, and when replacing a domain name (or any text without non-text characters in it) it doesn't make a difference. See also the note about using "extensive search" in the readme.

If you can share more details about the problem, such as the full error message you're getting or ideally a example which I can use to reproduce the issue, I might be able to look into it further.