Title: [Plugin: SyntaxHighlighter Evolved] Shortcodes being converted to html
Last modified: August 19, 2016

---

# [Plugin: SyntaxHighlighter Evolved] Shortcodes being converted to html

 *  Resolved [Scepter Marketing and Web Dev](https://wordpress.org/support/users/pyrocode/)
 * (@pyrocode)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/)
 * In reference to this post: [http://wordpress.org/support/topic/415959?replies=6](http://wordpress.org/support/topic/415959?replies=6)
 * It took a long time to find this solution and testing it, it seems to work. I’ve
   tried wrapping my code in [php], [sourcecode], and [html] (with closing tags 
   too by the way), which I am using the html option right now.
 * Very irritating trying to display “shortcode” samples on the front-end of the
   site because what was happening is that even though you can see the proper shortcode
   coding in the editor, as soon as I click save on the editor, the front-end displays
   the code but it converts the shortcode sample to it’s html version. No more shortcode
   square bracket tags, it’s html.
 * So seeing that other post, I decided to wrap each shortcode in a double square
   bracket and sure enough now it shows proper in the front-end.
 * So my question is, is this just how it works or is this a band-aid fix for a 
   bug with the plugin or WordPress or both?
 * [http://wordpress.org/extend/plugins/syntaxhighlighter/](http://wordpress.org/extend/plugins/syntaxhighlighter/)

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Contributor [viper007bond](https://wordpress.org/support/users/viper007bond/)
 * (@viper007bond)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/#post-1588835)
 * It’s not a bug, it’s just how WordPress works.
 * My plugin takes everything between it’s shortcodes and escapes it so that it 
   doesn’t render as HTML (i.e. `<` to `& lt;` and so forth). `[foobar]` doesn’t
   need escaping to be displayed like that, so it’s left alone.
 * WordPress then comes along later and sees the `[foobar]`, so it replaces it not
   realizing you didn’t want it replaced.
 * It’d be possible for my plugin to somehow escape all shortcodes within it’s shortcodes,
   but that’d be a huge undertaking. No thanks. 🙂
 *  Thread Starter [Scepter Marketing and Web Dev](https://wordpress.org/support/users/pyrocode/)
 * (@pyrocode)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/#post-1589098)
 * Thanks for the follow up Alex…I can understand the “huge undertaking” as I’ve
   discovered that working with WP for the past year has been quite the learning
   experience and I can easily say it’s a nightmare to develop for compared to working
   with a cms system like Joomla (which I enjoy working with for the last 4 years).
   I find it a lot easier.
 * Anyway, good to know about the shortcode part and finally after 2 hours of searching
   I found that solution. I can also say that your version of the syntaxhighlighter
   is the better one. Now if only the WordPress development team can work with the
   end-users instead of themselves, WP could have a more flexible and featured product
   🙂
 *  Plugin Contributor [viper007bond](https://wordpress.org/support/users/viper007bond/)
 * (@viper007bond)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/#post-1589103)
 * There’s no need to be a dick to me and the other people who contribute to the
   WordPress core. If you don’t like it, then don’t use it.
 * > I’ve discovered that working with WP for the past year has been quite the learning
   > experience and I can easily say it’s a nightmare to develop for compared to
   > working with a cms system like Joomla (which I enjoy working with for the last
   > 4 years). I find it a lot easier.
 * I didn’t say that and you likely only find it easier because you’re used to it.
   😉
 * BTW, WordPress allows you to escape shortcodes using double brackets:
 * [[shortcode]]
 *  Thread Starter [Scepter Marketing and Web Dev](https://wordpress.org/support/users/pyrocode/)
 * (@pyrocode)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/#post-1589104)
 * wow… not sure where that came from. Obviously took it the wrong way and wasn’t
   my intention. I was referring to me developing for WordPRess, not you or others.
   Ideally, it’s a developers environment and not a designers (which I am more of).
   Still, I stand by the fact it’s still a complicated system to develop for “me”
   and requires more programming and WordPress knowledge and experience coders
 * Anyway, and again, not sure where that sudden defensive statement came from, 
   but as I said, I was referring to myself experiencing a nightmare with learning
   the WP environment. In Design, there’s two areas: (1) designers (2) Developers….
   and both requires skills that it’s generally difficult to find someone who can
   do both equally well. A person will either be more of a designer or more of a
   developer (who lives for code).
 * Coffee time!
 *  Moderator [James Huff](https://wordpress.org/support/users/macmanx/)
 * (@macmanx)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/#post-1589105)
 * Hint: Alex is part of the WordPress development team and probably took offense
   when you said, “Now if only the WordPress development team can work with the 
   end-users instead of themselves, WP could have a more flexible and featured product.”
 *  [Strategerizer](https://wordpress.org/support/users/rneagu/)
 * (@rneagu)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/#post-1589180)
 * I tried to escape the gallery shortcode by putting it in double brackets and 
   as soon as I view the page in the Visual tab and save it, WP still processes 
   the gallery shortcode inside the outer brackets… any way to prevent it from doing
   that.
 * I assume that all WP devs with blogs would need to be able to escape shortcodes
   when explaining usage but I’ve been researching this for some time now and not\
   finding a reliable workaround.
 * Any suggestions?
 * [gallery](http://codex.wordpress.org/gallery)
 * (See above how it displays, even though I entered double brackets and below if
   I add backticks…)
 * `<a href="http://codex.wordpress.org/gallery">gallery</a>`

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘[Plugin: SyntaxHighlighter Evolved] Shortcodes being converted to html’
is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/syntaxhighlighter_ffffff.svg)
 * [SyntaxHighlighter Evolved](https://wordpress.org/plugins/syntaxhighlighter/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/syntaxhighlighter/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/syntaxhighlighter/)
 * [Active Topics](https://wordpress.org/support/plugin/syntaxhighlighter/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/syntaxhighlighter/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/syntaxhighlighter/reviews/)

 * 6 replies
 * 4 participants
 * Last reply from: [Strategerizer](https://wordpress.org/support/users/rneagu/)
 * Last activity: [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-shortcodes-being-converted-to-html/#post-1589180)
 * Status: resolved