Re: [PHP] 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 webthe way you want it!"
[EMAIL PROTECTED]
"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-
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Unserialize stopped working after php & db upgrade
If you've seen a serialised variable a few times, you get to know how one is set up and how to interpret it. If you're using serialised variables, I'd suggest serialising a few simple ones and see what the output looks like so that you can see when things are going amiss. This is one way that I debug things. Instead of var_dump()ing or print_r()ing something, I'll "echo serialize(...)". It's more compact than var_dump/print_r Martin -Original Message- From: Geoff Caplan [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 3:36 PM To: [EMAIL PROTECTED] Subject: [PHP] Unserialize stopped working after php & db upgrade 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, -- Geoff Caplan Advantae Ltd mailto:[EMAIL PROTECTED] http://www.advantae.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Unserialize stopped working after php & db upgrade
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, -- Geoff Caplan Advantae Ltd mailto:[EMAIL PROTECTED] http://www.advantae.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Unserialize stopped working after php & db upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey, There must be an error in the serialized stringswould you mind posting one for us to look at? How about posting some code? ~Pauly On Wednesday 18 September 2002 02:02 pm, you wrote: > Hi folks > > Bit of a major panic - any help MUCH appreciated. > > I have been storing serialized arrays in MySQL Gemini tables without > any problems. > > But with Gemini looking more and more like a dead duck, I decided to > take the server down and port from Gemini to InnoDB. I also took the > opportunity to upgrade from php 4.1 to php 4.2.2 > > Now, when I run unserialize( ) on the serialized arrays, the strings > are being returned unchanged. No error - they are simply passing > through unserialize( ) without being altered. > > It is not a backslash issue, as there are no escaped characters in the > strings affected, nor are the strings urlencoded. > > I have no idea how to go about fixing this and I am under serious > pressure to get the server back up ASAP - so I am very much hoping > that to get a response from the list. - -- ~Paul Nicholson Design Specialist @ WebPower Design "The webthe way you want it!" [EMAIL PROTECTED] "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 iD8DBQE9iM4vDyXNIUN3+UQRAmhGAJ9jAX88mO1F7MvFPTy/cB0jNf5d0ACeIaDb jOLego6+k2mIcplJ3y9uUNs= =a4Br -END PGP SIGNATURE- -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Unserialize stopped working after php & db upgrade
Hi folks Bit of a major panic - any help MUCH appreciated. I have been storing serialized arrays in MySQL Gemini tables without any problems. But with Gemini looking more and more like a dead duck, I decided to take the server down and port from Gemini to InnoDB. I also took the opportunity to upgrade from php 4.1 to php 4.2.2 Now, when I run unserialize( ) on the serialized arrays, the strings are being returned unchanged. No error - they are simply passing through unserialize( ) without being altered. It is not a backslash issue, as there are no escaped characters in the strings affected, nor are the strings urlencoded. I have no idea how to go about fixing this and I am under serious pressure to get the server back up ASAP - so I am very much hoping that to get a response from the list. -- Geoff Caplan Advantae Ltd mailto:[EMAIL PROTECTED] http://www.advantae.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
