"Invalid serialized data" - Size limit?

[jamieburchell]

Great tool. I've worked with 4KB - 8KB serliazed data successfully here https://serializededitor.com/, but 56KB of valid data seems to kill it. Is there a size limit/truncation? If so, it would be useful to mention it.

[Spreeuw]

I'm also getting this error with a 3066 character string (which I guess would be ~3kb?). The string in question serializes & unserializes with PHP without any problems but gives this error on https://serializededitor.com/. This string contains some sensitive data but I'd gladly send this to the developers if that helps to debug this issue.

[gilbitron]

What exactly is happening when you put too much data into it? Would you be able to send us the error you are seeing?

[jamieburchell]

It was a while ago but from what I remember the error is that the data is not valid/parsable but I did verify that it was. I suspect the data is truncated server side. Reaching POST size limits on the server perhaps.

[gilbitron]

@jamieburchell The data never get's sent to any servers (the app is entirely front-end JS only). I'll try testing with some large datasets and see if I can recreate.

[MihaiCraciun]

Got the same issue, invalid serialized data, figured out it happens because the data contains quotes.
PHP's unserialize has no issues with that because i think it uses the string length indicator to figure out if it should treat it as a separator.
here's the string

[a:9:{s:6:"active";b:1;s:7:"subject";s:32:"Contact Message "[your-subject]"";s:6:"sender";s:31:"[your-name] <[email protected]>";s:9:"recipient";s:17:"[email protected]";s:4:"body";s:149:"From: [your-name] <[your-email]>
Subject: [your-subject]

Message Body:
[your-message]

-- 
This e-mail was sent from a contact form on your website.";s:18:"additional_headers";s:22:"Reply-To: [your-email]";s:11:"attachments";s:0:"";s:8:"use_html";b:0;s:13:"exclude_blank";b:0;}](url)

[GaryJones]

When I tried it with data that contained markup with attributes with quotes (like the value of widget_custom_html from wp_options table), then it also reported it as invalid data. I didn't narrow it down to the minimum case to confirm this though.