HTML Entities displaying improperly as malformed escaped code

Turns out that this specific issue was caused by someone on the IT team who wasn’t very experienced with WordPress adding some code that they found on a poorly written WordPress blog that literally starts out with an unmarked example of what not to do.

According to the IT team, this line added to wp-config.php was apparently the cause of the issue:

define( 'CUSTOM_TAGS', true );

There are two morals to this story:

  1. Always read WordPress blogs critically and verify that what you are doing is really the BEST solution, not just a solution.
  2. Never assume that others will be careful about trusting random things they read on the internet. This includes WordPress blogs.

Related Posts:

  1. HTML encoding issues – “” character showing up instead of ” “
  2. What character encoding is >?
  3. How do we remove mystical [X] from text? Image included
  4. Add Attribute to p Tag of Post Content
  5. Inline style HTML attribute is being stripped from all elements of a post
  6. Why is WordPress swapping double quotes (“) to curly quotes (“) and how do I stop it from happening?
  7. Language selection for blog doesn’t exist?
  8. Redirect from an HTML page
  9. What is ' and why does Google search replace it with apostrophe?
  10. Should I use tag for icons instead of ? [closed]
  11. What’s the difference between HTML ‘hidden’ and ‘aria-hidden’ attributes?
  12. How do I vertically align text in a div?
  13. How do I vertically center text with CSS?
  14. How do I vertically center text with CSS?
  15. What does enctype=’multipart/form-data’ mean?
  16. Link with target=”_blank” and rel=”noopener noreferrer” still vulnerable?
  17. What does do?
  18. How to make JavaScript execute after page load?
  19. Parse error: Syntax error, unexpected end of file in my PHP code
  20. Is there a minlength validation attribute in HTML5?
  21. Getting rid of bullet points from
© 2024 Read For Learn