Whether you write plugins or hacks for WordPress, or you want to add bits and pieces of code about your own WordPress site or other programming code like HTML, CSS, PHP, or JavaScript, putting code in your post that looks like code, but doesn’t behave like code, is a frequent challenge for bloggers.
By default, the way a piece of code written or pasted to WordPress post editor is interpreted depends on whether you use visual or HTML post editor. Visual editor will consider the code to be an ordinary text, converting (encoding) the < and > characters into their < and > character entity equivalents, so that the code is not interpreted by a web browser. Quotes are converted too, but remember that by default, WordPress also applies auto-correction so that the text is quoted properly according to your language specifics. HTML editor does not convert any of these characters, so be aware that HTML and CSS markup you use in your code examples will be recognized by a web browser and you may end up with a funky looking text and a messed up layout.
Note that this behavior may differ with respect to the WordPress version, post editor and other plugins used. In some older versions of WordPress, unrecognized uses of the < and > characters were converted into the < and > character entities, and when an HTML tag was found within the post, the tag was left as it was, allowing for its interpretation in a web browser.
Code Within Paragraphs
The HTML tag which will turn text into a monospaced
font. They are <code> and <tt>. The latter is rarely used today, replaced by the more useful and semantically correct <code>, which distinguishes text that is computer code from natural language.
This is an example which mentions code within a paragraph,
namely the functions <code>wp_title()</code>,
<code>wp_content()</code> and <code>wp_footer()</code>,
which are very useful in WordPress.
This is great for making a piece of non-HTML text look like code, but what about HTML tags that you want to showcase?
In the header.php template file,
look for the <code><div class="header"></code>
section to change the <code><h1></code> heading.
Using the <code>
tag doesn’t tell WordPress to encode HTML markup within the tag or strip it from the post. WordPress thinks that you are using this markup for formatting, leaving it untouched. A web browser then sees a <code>
tag followed by a <div>
tag and so it responds by creating a new container in your web page.
To avoid this behavior, use character entities or extended characters to represent the left and right arrow characters in a way that is not recognized as the beginning and end of an HTML tag by a web browser, like this:
In the header.php template file,
look for the <code><div class="header"></code>
section to change the <code><h1></code> heading.
URLs Within Paragraphs
By default, WordPress will turn any phrase that begins with http: into a link. If you are giving an example of how to link to a specific post within a WordPress site, instead of using the link with http://example.com/index.php?p=453
and having it turn into a link, you can use extended characters for the slashes, so WordPress won’t “see” the link:
...link to a specific WordPress post using
<code>http:& amp;#47;& amp;#47;example.com& amp;#47;index.php?p=453</code>
in your post....
Note: Take off Space between ‘&’ and ‘amp’.
List of Related Character Entities
Here is a list of some HTML character entities related to the topic of this article:
(less than) = < or < (greater than) = > or > / = / ] = ] [ = [ " = " or " ' = ' “ = “ or “ ” = ” or “ ‘ = ‘ or ‘ ’ = ’ or ’ (ampersand) = & or &
There is a list of resources below which will help you turn HTML tags into character entities automatically, so you don’t have to memorize these character codes.
Using the <pre> tag
To set your code aside so that it looks like a box of code which may be copied and pasted within other code or template file, you can use the <pre> HTML tag.
The <pre> tag instructs the browser to use a monospaced font, but to exactly reproduce whatever is inside of the <pre>tags. Every space, line break, every bit of code is exactly reproduced.
<h3>Section Three Title</h3>
<p>This is the start of a
<a title="article on relationships" href="goodtalk.php">
good relationship</a> between you and me....
Using the <pre> tag isn’t very “pretty” but it does the job. Examples of how to style it can be found in the next section. Still, it showcases the code exactly.
By exactly, we mean EXACTLY. If you have a long line of code, it will run off the page because there are no instructionswhich tell the code to wrap. It won’t. Here is an example:
<h3>Section Three Title</h3><p>This is the start of a <a title="article on relationships"
href="goodtalk.php">good relationship</a> between you and I and I think you should read it because it is
important that we have these little <a title="article on communication"
href="communication.php">conversations</a> once in a while to let each other know how we feel....
Not pretty, is it. To avoid this screen run-off, put in line breaks. Unfortunately, deciding where to put those line breaks in when you are showcasing code that will be copied makes it a difficult decision.
If you are familiar with programming language, you will know when a line break won’t mess up a line of code, so choose there. If you are unfamiliar with where to put line breaks, experiment. Put the code in, make the line breaks, and then test the code. If it works, then use the line break there. If not, change the line break position.
If you have long lines of code, consider showcasing only excerpts and providing a link to the full code placed on your site in a text or PHP file, or using one of the many online pastebins which are available for temporarily showcasing code.
Troubleshooting Codes
Writing code within a WordPress post can be a challenge, maybe forcing you to override the WordPress default styles and to use filters which “fix” what we write. If you are having trouble with writing code within your WordPress post, this section might help.
Quotes Auto-correction
A frequent problem when using codes within your post is the quotes auto-correction feature of WordPress, mostly known from word processing software. By default, when serving a web page, WordPress converts the “straight“ quotes into the opening and closing “curly” quotation marks according to your WordPress installation language set in the wp-config.php file. Note that the auto-correction (also called smart quotes) feature is applied regardless of whether you have written the quotes in visual or HTML post editor.
In HTML post editor, you can avoid this problem by wrapping the quotes with the <code>, <tt> or <pre> tags. Other solution is replacing quotes with their respective character entities, e.g. using:
<code><p class=& #34;red& #34;></code> // Take off space between & and #
instead of:
<p class="red">
Note that in some older versions of WordPress, if you edited a page again after publishing it, the HTML editor replaced all these entities with their literal equivalents. For example, if you carefully used " for your quotes, they would have come back as “, and if saved, the auto-correction feature would have an effect on them.
Resources
Frequent Code User
If you consistently use a lot of formulas, functions, and programming code in your posts, consider using a plugin or PHP tool to make the entire process easier. If you tend to post a LOT of code blocks, consider pasting the code in a Paste Bin and linking to it on your site.
- FigureRender – LaTeX rendering plugin
- 9 Syntax Highlighter Plugins and Services for Embedding Code Snippets in WordPress – Following are list of best WordPress plugins or 3rd-party services to highlight code snippets within your blog that I have personally tried in 2013.
- Coffee2code’s Preserve Code Formatting WordPress Plugin
- QuickCode WordPress Plugin – Hides/unhides formatted blocks of code.
- Using ASCIIMath
- LaTex – A document preparation system
- Using LaTeX in WordPress
- Display mathematical equations within your posts
- How to Build Dean Lee’s Plugin – A plugin for GeSHi – Generic Syntax Highlighter
- Visual Code Editor Plugin – Modifies WordPress’s behavior so that code format is preserved when using the visual editor. It will work with any syntax highlighter that accepts encoded/escaped syntax.
- SyntaxHighlighter Evolved – allows you to easily post syntax-highlighted code to your site without having to escape the code.
Was this article helpful? How could it be improved?
Log in to submit feedback. If you need support with something that wasn't covered by this article, please post your question in the support forums.