WPIntell

Source evidence

Validation Error

Squelch Unspam · support · 2015-05-15T23:53:00+00:00

complaintsentiment
highseverity
0.96relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 32 rows with source links

15.6% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

27 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Anonymous User 14247956 unresolved
Hello. I’m using WordPress 4.2.2 and the latest version of this plugin (1.3) gets one validation error, as follows: Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.) <style type=”text/css”> Here is the faulty code: <style type=”text/css”> body #commentform #l1u9y, body #commentform #rwzad, body #commentform #k7oft, body #commentform #yd21e { display: none;} #commentform input, #commentform textarea { display: none;} </style> How can I fix it? The solution is very simple, I suppose. P.S: The previous version worked fine. Thanks. https://wordpress.org/plugins/squelch-unspam/ Oh my apologies, WordPress.org didn’t notify me of this post so I’ve only just chanced upon it. Are you still having this issue? That particular error is typically indicative of an unclosed <div> tag or similar. The code being injected into your page by Unspam should not be triggering that particular warning/error. Hi Matt. Sorry for no reply in time. I solved the issue by downgrading to version 1.22. That would resolve your issue, but only because there would be no injected CSS or JS. The older versions of this plugin have some bugs that drastically reduce its effectiveness in preventing spam so it’d definitely be better to upgrade. If you can upgrade and then let me have a link to the page that has the problem then I can take a look into it for you. If the issue is with Unspam I can then roll out an update.

Comments

3 shown
Matt Lowe 2015-11-25T14:21:00+00:00

Oh my apologies, WordPress.org didn’t notify me of this post so I’ve only just chanced upon it. Are you still having this issue? That particular error is typically indicative of an unclosed <div> tag or similar. The code being injected into your page by Unspam should not be triggering that particular warning/error.

Anonymous User 14247956 2016-02-20T16:33:00+00:00

Hi Matt. Sorry for no reply in time. I solved the issue by downgrading to version 1.22.

Matt Lowe 2016-02-22T11:05:00+00:00

That would resolve your issue, but only because there would be no injected CSS or JS. The older versions of this plugin have some bugs that drastically reduce its effectiveness in preventing spam so it’d definitely be better to upgrade. If you can upgrade and then let me have a link to the page that has the problem then I can take a look into it for you. If the issue is with Unspam I can then roll out an update.