Re: Unserialize stopped working after php & db upgrade

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Geoff, I looked at the string..... s:1745:"s:1735:"s:1725:"s:1715:"s:1705:"s:1695:"s:1685:"s:1675:"s:1665:"s:1655:"s:1645:"s:1635:"s:1625:"s:1615:"a:2:{ see all of the s's? It means that unserializer will produce a string that looks like was not unserialized(but it was). So, I just deleted everthing to the 'a' and removed everything past the last } at the end. I'm glad it worked out for you:) ~Pauly On Thursday 19 September 2002 01:35 am, Geoff Caplan wrote: > Paul, > > PN> It looks like that string has been serialized multiple times > > Many thanks - that is the problem! I think that this qualifies as one > of my more creative bugs... > > Can I ask you how you spotted this? Pretty impressive, considering you > only had the string itself to go on. > > Thanks again, - -- ~Paul Nicholson Design Specialist @ WebPower Design "The web....the way you want it!" paul@webpowerdesign.net "It said uses Windows 98 or better, so I loaded Linux!" Registered Linux User #183202 using Register Linux System # 81891 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9id2SDyXNIUN3+UQRApeyAJ4ohHufAZW6A4Sn1jY+YI2X0RvGZACeJGyp t5/CIlMx9O8fWWQSld3krRI= =a36C -----END PGP SIGNATURE-----