unserialize() error in mediamose_response.inc

08Jun2012 Posted by UvA-Tom

I've encountered multiple entries in apache error_log regarding php unserialize() error. Here's an example:

[Fri Jun 08 15:45:44 2012] [error] [client xx.xx.xx.xx] In /var/www/html/sites/all/modules/mediamosa/response/mediamosa_response.inc at line 535; unserialize(): Error at offset 0 of 1 bytes (function: )mediamosa_response->generate_xml_add_child().

Any idea what could be causing this? Running 2.3.17.

Comments

.

Posted by Robert on June 8th, 2012 - 15:52

Its caused by code that adds attributes to a XML tag. The XML attributes are stored as serialized data during the XML generation.

Its a way I really regret that I ever wrote into the engine, at the time it was the best option. Its on my list for MM3.5 to get rid off.

You can find the cause by searching for

['#' . serialize(array('

If you are able to figure out which REST call is causing it (guessing /asset/[id]), then you might find what data is causing it by turning off those found hits on

['#' . serialize(array('

and I might be able to help you further with fixing it.

There should be 4 places in code where this serialize trick is used.

I can't say if 3.x will fix your notice however, as the notice is caused by specific data in your database, its not directly code related.

Hi Robert, Thank you for you

Posted by UvA-Tom on June 9th, 2012 - 09:29

Hi Robert,

Thank you for your quick response. Indeed these errors are triggered by /asset/$assetid requests.
Should I search the whole codebase, or specific modules?

You said: "If you are able to figure out which REST call is causing it (guessing /asset/[id]), then you might find what data is causing it by turning off those found hits on
['#' . serialize(array('
"
I don't understand it, what should be replaced with what?

Just comment out the whole

Posted by Robert on June 11th, 2012 - 09:08

Just comment out the whole line, it will not break anything (well not server side) and see if the notice goes away. Once it does, then let me know which one you commented out. Then the next step is what kind of data it tries to serialize (by logging the data) and why it gives the notice. But I'll provide you the code for that as soon as I know where in the code this notice happens.