Closed truth4oll closed 9 years ago
Hi! Could you provide more info on this error. I use this way to store serialized data for about 5 years without any problems.
Oh, I think I know what you mean. The problem appears when you use non-UTF8 encoding in your database. Ok, I'll add this feature soon.
Your example is not about DB, it’s on submission of serialized data with HTML forms. Here is more related one: http://www.jackreichert.com/2014/02/02/handling-a-php-unserialize-offset-error/
As I said, there’s no problem when you use UTF8 in the DB.
Save serialized data in database through base64_encode, and get through base64_decode. It helps avoid popular error with offset