We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Save serialized data in database through base64_encode, and get through base64_decode. It helps avoid popular error with offset
The text was updated successfully, but these errors were encountered:
Hi! Could you provide more info on this error. I use this way to store serialized data for about 5 years without any problems.
Sorry, something went wrong.
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.
for example http://php.net/manual/en/function.serialize.php#47509
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.
c3bf33b
baibaratsky
No branches or pull requests
Save serialized data in database through base64_encode, and get through base64_decode.
It helps avoid popular error with offset
The text was updated successfully, but these errors were encountered: