Replace Content in PRE Tags with HTML Entities
If you have a website that relies heavily on PRE tags, you know the important of converting PRE tag content to their HTML entities. Doing so prevents worlds of possible rendering issues. The following PHP snippet HTML-Entitizes (?) any code within PRE tags:
//replaces pre content with html entities
function pre_entities($matches) {
return str_replace($matches[1],htmlentities($matches[1]),$matches[0]);
}
//to html entities; assume content is in the "content" variable
$content = preg_replace_callback('/<pre.*?>(.*?)<\/pre>/imsu',pre_entities, $content);
I use this for just about every post I write. You could also stick this in your CMS if you have clients that may have use for PRE tags.
![Create a CSS Flipping Animation]()
CSS animations are a lot of fun; the beauty of them is that through many simple properties, you can create anything from an elegant fade in to a WTF-Pixar-would-be-proud effect. One CSS effect somewhere in between is the CSS flip effect, whereby there's...
![Creating Scrolling Parallax Effects with CSS]()
Introduction
For quite a long time now websites with the so called "parallax" effect have been really popular.
In case you have not heard of this effect, it basically includes different layers of images that are moving in different directions or with different speed. This leads to a...
![Using Opacity to Show Focus with MooTools]()
I'm a huge fan of using subtle effects like link nudging (jQuery, MooTools) to enhance the user experience and increase the perceived dynamism of my websites. Trust me -- a lot of little things are what take websites to the next level.
![dwImageProtector Plugin for jQuery]()
I've always been curious about the jQuery JavaScript library. jQuery has captured the hearts of web designers and developers everywhere and I've always wondered why. I've been told it's easy, which is probably why designers were so quick to adopt it NOT that designers...
Beware that having someting like “something” in another would leave you with one opening and two closings. If this is a possible usecase, you might use a regex like this :
/(.*?[.*]*)/imsu
…but it still wouldn’t handle the case of having a single closing tag inside another . Could someone manage to write a regex which would handle this case ?
The function name (pre_entities) should be between quotes otherwise it will throw a notice.
Beware that having a pre tag inside another pre tag would leave you with one pre opening and two pre closings. If this is a possible usecase, you might use a regex like this :
/<pre.*?>(.*?[<pre.*?>.*<\/pre>]*)<\/pre>/imsu
The tags got stripped in my first comment, sorry about that, if htmlentities show up in the regex, replace them with the good characters …but it still wouldn’t handle the case of having a single closing pre tag inside another pre. Could someone manage to write a regex which would handle this case ?
The function name (pre_entities) should be between quotes otherwise it will throw a notice.
It works as long as you don’t have nested <pre> tags.
I wrote about this on my blog but the only real way to do it is to use an XML parser.
One issue to watch out for is to not encode any of the content before this is run, as it will double-entitize the ampersand e.g., &.
Also, would there be any issues if not matches are found?
To solve the nested ‘pre’ tag issue, just use some non-standard tags that you’re sure won’t be in your content, rather than ‘pre’ (i.e. ‘mycode’). Your regular expression then becomes a match for the ‘mycode’ tags, and you can immediately follow it up with another preg_replace () to turn the ‘mycode’ tags into ‘pre’ tags after you’re done htmlentitizing the content.
I’ve been using elliotswan.com/postable. It seems to get the job done for me. But it’s nice to know this option.
Could someone explain how to fix the following notice?
Notice: Use of undefined constant pre_entities – assumed ‘pre_entities’ in C:\wamp\www\example.com\admin\get_posts.php on line 16
doh! put quotes on ‘pre_entities’, fixes it. Thanks David! Great snippet.
Thank you for the tip! I couldn’t find what was going wrong with the HTML…