Comments on: PHP: unserialize() Error at offset… (simple solution) http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/ things I learn, as I learn them Sat, 04 Feb 2012 01:35:33 +0000 hourly 1 http://wordpress.org/?v=3.1 By: A Free wordpress newsletter » unserialize() Error at Offset… Different solutions http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-16210 A Free wordpress newsletter » unserialize() Error at Offset… Different solutions Thu, 15 Dec 2011 03:10:10 +0000 http://ryanbosinger.com/blog/?p=95#comment-16210 [...] others prefer to use [...] [...] others prefer to use [...]

]]> By: wp-coder.net » unserialize() Error at Offset… Different solutions http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-16209 wp-coder.net » unserialize() Error at Offset… Different solutions Thu, 15 Dec 2011 03:06:52 +0000 http://ryanbosinger.com/blog/?p=95#comment-16209 [...] others prefer to use [...] [...] others prefer to use [...]

]]> By: unserialize() Error at Offset… Different solutions | WPhub.biz http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-16204 unserialize() Error at Offset… Different solutions | WPhub.biz Wed, 14 Dec 2011 19:19:58 +0000 http://ryanbosinger.com/blog/?p=95#comment-16204 [...] others prefer to use [...] [...] others prefer to use [...]

]]> By: Josh Sommers http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-14928 Josh Sommers Tue, 19 Jul 2011 03:24:52 +0000 http://ryanbosinger.com/blog/?p=95#comment-14928 I was getting the same error while using CodeIgniter. Adding trim() before trying to unrealized worked beautifully. Not sure if it matters, but I didn't get this until migrating from Ubuntu 8.04 to Ubuntu 10.04. Thank you for the awesome time saving tip! Aloha - Josh I was getting the same error while using CodeIgniter. Adding trim() before trying to unrealized worked beautifully. Not sure if it matters, but I didn’t get this until migrating from Ubuntu 8.04 to Ubuntu 10.04.

Thank you for the awesome time saving tip!

Aloha – Josh

]]> By: Damo http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-11805 Damo Sun, 16 Jan 2011 02:29:09 +0000 http://ryanbosinger.com/blog/?p=95#comment-11805 It seems the problem is in fact something to do with CodeIgniter, I've been using serialize()/unserialize() for a few years now and never had this problem until I recently started using CI. Thanks for the fix :) It seems the problem is in fact something to do with CodeIgniter, I’ve been using serialize()/unserialize() for a few years now and never had this problem until I recently started using CI. Thanks for the fix :)

]]> By: frostymarvelous http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-11307 frostymarvelous Sat, 11 Dec 2010 10:25:12 +0000 http://ryanbosinger.com/blog/?p=95#comment-11307 I figured out what was causing the error so I figured I'd post it just in case. You were right, there were some bytes after all. Seems the editor I was using threw in a few bytes at the beginning of the document when I saved as UTF-8. This is known as BOM (byte order marker). Luckily, it has an option to save UTF-8 without the BOM. That solved the issue. Seems notepad does this also but doesn't have the option to save without BOM. The editor I used is notepad++. One of the best freeware I should add. On a related issue, this also causes the session_start() headers cannot already sent error. That's how I actually figured it out. Hope this helps. I figured out what was causing the error so I figured I’d post it just in case.
You were right, there were some bytes after all. Seems the editor I was using threw in a few bytes at the beginning of the document when I saved as UTF-8. This is known as BOM (byte order marker). Luckily, it has an option to save UTF-8 without the BOM. That solved the issue.
Seems notepad does this also but doesn’t have the option to save without BOM. The editor I used is notepad++. One of the best freeware I should add.
On a related issue, this also causes the session_start() headers cannot already sent error. That’s how I actually figured it out.
Hope this helps.

]]> By: frostymarvelous http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-11288 frostymarvelous Thu, 09 Dec 2010 18:28:48 +0000 http://ryanbosinger.com/blog/?p=95#comment-11288 Well, I was using curl to get the echoed data. Worked fine till I changed all the encodings of all pages to UTF-8. I think I might have missed some, not sure. But then I later tried and there it was, the same error. I fixed it by echoing a base64 encoded string, and then decoding it after. Trim() didn't work for me however, so I thought I should post this for others. Well, I was using curl to get the echoed data.
Worked fine till I changed all the encodings of all pages to UTF-8. I think I might have missed some, not sure.
But then I later tried and there it was, the same error.
I fixed it by echoing a base64 encoded string, and then decoding it after. Trim() didn’t work for me however, so I thought I should post this for others.

]]> By: Minh Tuan http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-11250 Minh Tuan Mon, 06 Dec 2010 08:26:23 +0000 http://ryanbosinger.com/blog/?p=95#comment-11250 Sorry. my mean database field charset. utf8_general_ci for example Sorry. my mean database field charset. utf8_general_ci for example

]]> By: Minh Tuan http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-11249 Minh Tuan Mon, 06 Dec 2010 08:23:33 +0000 http://ryanbosinger.com/blog/?p=95#comment-11249 another case: check your database field encode another case: check your database field encode

]]> By: Melli http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-9436 Melli Mon, 17 May 2010 09:06:30 +0000 http://ryanbosinger.com/blog/?p=95#comment-9436 I just want to say Thanks, The trim() solution did not work in my case, but your advice put me on the path to what I believe is at the heart of this problem- database field lenght. As it turns out, serialize() will include a few control characters with the data. If the field lenght is too small, those control characters will be truncated with no error from the system that they were not included with your data. As it is, the bug dont show up until you are trying to retrieve the data with the "unserialize()" function. Of course, with some of the control characters missing, the retrieval fails. This also explains, why trim() will work in some cases, depending on how much white space is can be removed with the trim(). For a permanent fix, increase the feild lenght in the database by a few characters to include the serialize control characters especially so if the data to be stored will vary in size. I just want to say Thanks,
The trim() solution did not work in my case, but your advice put me on the path to what I believe is at the heart of this problem- database field lenght. As it turns out, serialize() will include a few control characters with the data. If the field lenght is too small, those control characters will be truncated with no error from the system that they were not included with your data. As it is, the bug dont show up until you are trying to retrieve the data with the “unserialize()” function. Of course, with some of the control characters missing, the retrieval fails. This also explains, why trim() will work in some cases, depending on how much white space is can be removed with the trim(). For a permanent fix, increase the feild lenght in the database by a few characters to include the serialize control characters especially so if the data to be stored will vary in size.

]]>