content:encoded should not contain onclick attribute
-
Our daily newsletter is created by reading our site’s RSS feed. Recently we started having issues with customers not getting any content, only the unsub message. We were told by our newsletter maker (MailChimp) that the issue is with the onclick.
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
*line 36, column 0: content:encoded should not contain onclick attribute (95 occurrences)
I looked at the “solution” for this and it stated:
Consider removing the potentially unsafe HTML attribute. At a minimum, ensure that your content will still display as intended if this attribute is stripped by security conscious clients.
When I look at the HTML code that we have input, there are no occurrences of onclick, so this is something that WordPress is creating itself.
How do I tell WordPress to NOT include the onclick?
- The topic ‘content:encoded should not contain onclick attribute’ is closed to new replies.