I have a few Serialized PHP queries that seemed to have stopped working today.  It may have been as a result of the recent update.  They were working yesterday.  The structure of the return serialized data from php looks visually proper.  Has there been a change to the Serialized PHP section?

Here is the serialize data that wpdatatables says has no rows:

a:1:{i:0;a:7:{s:4:"Name";s:11:"A1 Towing";s:18:"Subscription Hours";i:40;s:12:"90 Days Supp";d:50;s:6:"7 Days";d:-4.79999999999999982236431605997495353221893310546875;s:7:"30 Days";d:-11.800000000000000710542735760100185871124267578125;s:7:"90 Days";d:-50.7999999999999971578290569595992565155029296875;s:7:"Balance";d:78.5199999999999960209606797434389591217041015625;}}

Actually, this is more correct.  I had to remove a company name and I replaced with wrong number of characters in last post.

a:1:{i:0;a:7:{s:4:"Name";s:11:"A1 Towing A";s:18:"Subscription Hours";i:40;s:12:"90 Days Supp";d:50;s:6:"7 Days";d:-4.79999999999999982236431605997495353221893310546875;s:7:"30 Days";d:-11.800000000000000710542735760100185871124267578125;s:7:"90 Days";d:-50.7999999999999971578290569595992565155029296875;s:7:"Balance";d:78.5199999999999960209606797434389591217041015625;}}

Aleksandar,

Thank you for the reply.  Due to the nature of the information, I cannot share it.  I finally just switched the output to JSON and I have my tables back.  I won't use the serialized option.

I am still not sure what is causing the issue.  If I manually use a browser to read the serialized array, perform a copy all and paste back into an echo of a different php file, wpdatatables is able to read the serialized array.  I am not sure what may be different between the generated and echoed streams.  When I look at the html of both examples, they look identical with same headers and data. The byte count is the same. A file compare reveals no differences.  It is difficult to understand what may be the issue because all I see is "Table in data source has no rows." on the generated stream.

You can close this ticket.  I will use json from now on.

Regards,

Gerard