- Issue created by @guardiola86
- First commit to issue fork.
- Merge request !102Issue #3425257: Notice: unserialize() issue fixed → (Closed) created by himanshu_jhaloya
- last update
about 1 year ago 372 pass - 🇺🇸United States DamienMcKenna NH, USA
DamienMcKenna → changed the visibility of the branch 3425257-unserialize-error to hidden.
- Status changed to Needs review
about 1 year ago 3:02pm 4 March 2024 - last update
about 1 year ago 372 pass - 🇺🇸United States DamienMcKenna NH, USA
How about this instead?
I suspect the value in the database got corrupted somehow.
FYI in 2.0.x it hides the response from unserialize() if it's not in the correct format.
- 🇪🇸Spain guardiola86
The issue happens when adding emojis in the meta description apparently. Not sure if that's fixed in version 2.x.
- 🇺🇸United States DamienMcKenna NH, USA
Can you please get an example string from the database so that we can see what's going on? Emojis should save just fine.
- 🇺🇸United States DamienMcKenna NH, USA
If emoji don't save properly, or aren't loaded properly, then I wonder if there's a problem with the database table's definition, rather than it being a problem with the module? Do you have any way of checking the table's collation? It should probably be "utf8mb4_general_ci".
I get this too, but seemingly only when I run cron. And it appears about 20 times. It will happen on any page, node or not, when I run cron.
- 🇺🇸United States nkraft
I upgraded to the latest version of the module today, and started seeing this (or a very similar message) on my homepage.
- 🇮🇳India JatinGupta40
I also upgraded the module to 1.26 version.
I tried to apply patch #7, and it didn't work.While tested as of now, the array is in the json format instead of being PHP serialized string.
Will try to resolve and create a patch for it.Thanks.