SyntaxHighlighter Evolved preserves the formatting of your syntax-highlighted code while allowing you to easily post it on your website. No manual changes required!
Block: Switch to server-side rendering so that the same code that renders the shortcode will render the block.
Version 3.4.2
Blocks: Support SyntaxHighlighter block being used as a reusable block.
Version 3.4.1
Bring back support for the Gutenberg plugin for the people that are still on older versions of WordPress (pre-5.0) and are using the new block editor via the Gutenberg plugin.
Version 3.4.0
Drop support for the Gutenberg plugin in favor of WordPress 5.0’s native functionality (different function names).
Version 3.3.2
Gutenberg: If a language isn’t selected in the block configuration, default to plain text.
Version 3.3.1
Make sure wp-editor script is loaded for Gutenberg.
Version 3.3.0
Gutenberg block thanks to @iandunn.
Add a few extra keywords to the JavaScript highlighter. Props @caitp.
Version 3.2.1
Fix shortcode issues that would occur during post editing if the code contained what looked like opening HTML tags such as <?php. See this forum thread for details.
Version 3.2.0
Don’t parse shortcodes inside of HTML entities, which could result in broken HTML.
Drop PHP4 support. This should result in PHP7 support.
Version 3.1.13
Fix setting sanitization bug. Props Alexander Concha (@xknown).
Don’t encode shortcode contents on (un)trash. Props Andrew Ozz (@azaozz).
Version 3.1.12
Updated editor JavaScript for WordPress 4.3. Props Andrew Ozz (@azaozz).
Fix a bug that prevented highlighting a range of lines, such as “5-10”.
Version 3.1.10
New version of SyntaxHighlighter 3.x library to address XSS security issue. Props Ben Bidner for finding the bug and Alex Gorbatchev working with us (Automattic) to patch the issue.
Compatibility with moving the plugins folder to a location other than the default one.
Updated Japanese translation file thanks to Daisuke Takahashi.
Version 3.1.9
Reset box-shadow property for better theme support. Props Michael Fields.
XHTML validation fix by adding type attribute to <style> tag. Props NoMad1337.
Version 3.1.6
Kill off v2 copy-to-clipboard SWF file due to XSS security issue with the file. If you want to be able to copy/paste, use the better v3.
Switch from using a <meta> tag to a <style> tag as the JavaScript anchor in the <head>. This should fix the validation error under HTML5.
Remove an old forced font-size function — it wasn’t actually used.
Remove references.
Version 3.1.5
The slashing changes made in WordPress 3.6 (alpha) have been reverted — we’re back to the old way again. This release restores the code back to Syntaxhighlighter v3.1.3. See ticket #21767.
Version 3.1.4
WordPress 3.6 (alpha) compatibility. Content is now being stripped of slashes before being run through filters so this plugin needs to stop trying to strip slashes and then adding them back. See ticket #21767.
Version 3.1.3
Hide vertical overflow so that a vertical scrollbar doesn’t show up in Chrome. Props Caio Proiete. Bump SH script version to bust browser caches.
Allow the plugin’s shortcodes to be escaped using double brackets like so: [[code]Foobar[/code]]. This is a core feature, but calling do_shortcode() on the content as it went into the database caused the extra brackets to be stripped.
Version 3.1.2
Register some placeholder shortcodes so that strip_shortcodes() and such work properly. Previously the shortcodes were only registered during the brief moment that they were processed by one of this plugin’s filters.
Add a notranslate CSS class to the <pre> output so that Google won’t attempt to translate it. Props Otto.
Run the CSS classes aka SyntaxHighlighter script parameters through a filter.
Version 3.1.1
Fix default title setting not working.
Force <code> to be inline. Fixes issues with themes that do code { display: block; }.
Disable [latex] to avoid collisions with LaTeX rendering plugins. Use [tex] instead if you want to post LaTeX source.
Version 2.3.7
Add a checkbox to settings page to force all language brushes to always be loaded, even if they aren’t needed. This is incase anyone wants to use the <pre> tags directly (without the shortcode), for example if they use this Windows Live Writer plugin.