In the latest 7.2.16 EE version, when I click to see the spam comments caught, I get the following warning…
Warning Erroneous data format for unserializing 'ExpressionEngine\Model\Comment\Comment' ee/ExpressionEngine/Service/Model/Column/Serialized/Native.php, line 27 Severity: E_WARNING Notice unserialize(): Error at offset 49 of 1113 bytes ee/ExpressionEngine/Service/Model/Column/Serialized/Native.php, line 27 Severity: E_NOTICE
Any ideas about what’s that warning about and more importantly how to get rid of it, please? Thanks!
Hi @Daem0n - does the page load, or all that you see are the warning?
Do you know if the comment trapped actually exists - or it has been removed by other means?
Also, what EE version did you upgrade from? Did you have Spam module installed previously?
(unable to replicate the issue so far)
Hi @Yuri 👋
Yes, the page loads (can’t seem to be able to upload a file here so here’s a link to a full-page screenshot in case this helps more). I’ve been regularly upgrading my site to the latest version since v5 or v6 (don’t remember my initial installation version number). The comment in the spam trap is there since before my latest upgrade. I was getting the error before as well, but I was hoping that a future version will resolve the issue. That didn’t happen, hence my post here.
Not sure if it’s useful/relevant or not, but I have “Require CAPTCHA?” enabled, as well as “Use reCAPTHCA v3?”.
Here is exp_comments, and here’s exp_spam_trap.
Some additional info in case it helps anyone who knows more than me to debug this…
I tried selecting the comment while in the spam trap and marking it as spam (the same happens if I mark it as not spam) and here’s what I got. This means that I can’t get rid of this comment in any way. The weird thing is that I was able to mark as “Spam” or “Not Spam” other comments caught by the spam trap. Any ideas about what could be so special about this particular comment?
For the time being (if you want to whitelist this comment), you can just remove this record from
exp_spam_trap and change the comment’s status to
o (open) in
c for closed)
Thank you, Yuri! That did the trick and removed the comment from the spam trap.
I’m still not sure what was so special about that comment that made it stuck with the above error but at least other comments caught by the spam trap don’t produce the same error. So I guess this is… resolved? 🤷♂️
Resolved… for now 😊
Please post back if you face the issue again, then maybe we could replicate and fix in the code!
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.