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 Fri, 03 Sep 2010 22:00:08 -0400 http://wordpress.org/?v=2.9.2 hourly 1 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.

]]> By: Joshua Powell http://ryanbosinger.com/blog/2009/php-unserialize-error-at-offset-simple-solution/comment-page-1/#comment-9248 Joshua Powell Tue, 27 Apr 2010 01:06:49 +0000 http://ryanbosinger.com/blog/?p=95#comment-9248 Thanks for the fix, worked out great for me. Kept getting that pesky "Error at offset" error. I have been programming with PHP for at least 5 years and I have never come across this error until now. You mentioned you were using Codeigniter because this is the first time I have run into the error and I was using Expression Engine which is based on Codeigniter. Again thanks for the tip. Using trim() worked great. Thanks for the fix, worked out great for me. Kept getting that pesky “Error at offset” error.

I have been programming with PHP for at least 5 years and I have never come across this error until now. You mentioned you were using Codeigniter because this is the first time I have run into the error and I was using Expression Engine which is based on Codeigniter.

Again thanks for the tip. Using trim() worked great.

]]>