<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 07:15:41 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Alan Skorkin's Blog: How To Fix The WP-Syntax Special Character Escaping Issue]]></title>
      <guid>http://www.phpdeveloper.org/news/14167</guid>
      <link>http://www.phpdeveloper.org/news/14167</link>
      <description><![CDATA[<p>
<i>Alan Skorkin</i> has a recent post to his blog about a trouble that many WordPress users have come across in working with their content and the <a href="http://wordpress.org/extend/plugins/wp-syntax/">WP-Syntax</a> plugin (for displaying code) - a special character escaping bug that escapes characters that don't need it.
</p>
<blockquote>
Suffice to say, [WP-Syntax] does the job fine except for one very annoying issue. Whenever you have any kind of special characters in your code (which you inevitably do e.g. <, >, & etc.), these always render as their escaped representations.
</blockquote>
<p>
It only happens with the WYSIWYG editor for writing content (which the tool's FAQ recommends turning off) but there's a better solution that <i>Alan</i> found - change a line of code in the plugin to use the <a href="http://php.net/htmlspecialchars_decode">htmlspecialchars_decode</a> function to rid your install of this pesky escaping bug.
</p>]]></description>
      <pubDate>Thu, 11 Mar 2010 09:15:21 -0600</pubDate>
    </item>
  </channel>
</rss>
