Title: Garth Gutenberg's Replies | WordPress.org

---

# Garth Gutenberg

  [  ](https://wordpress.org/support/users/dosboy/)

 *   [Profile](https://wordpress.org/support/users/dosboy/)
 *   [Topics Started](https://wordpress.org/support/users/dosboy/topics/)
 *   [Replies Created](https://wordpress.org/support/users/dosboy/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/dosboy/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/dosboy/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/dosboy/engagements/)
 *   [Favorites](https://wordpress.org/support/users/dosboy/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Easy Random Posts] [Plugin: Easy Random Posts] Hard To Follow Instructions](https://wordpress.org/support/topic/plugin-easy-random-posts-hard-to-follow-instructions/)
 *  [Garth Gutenberg](https://wordpress.org/support/users/dosboy/)
 * (@dosboy)
 * [15 years, 5 months ago](https://wordpress.org/support/topic/plugin-easy-random-posts-hard-to-follow-instructions/#post-1567370)
 * FWIW, Easy Random Posts has been updated to include both a shortcode and a widget,
   so editing your theme directly is no longer required.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SyntaxHighlighter Evolved] [Plugin: SyntaxHighlighter Evolved] Problems with IE and Chrome Browsers](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-problems-with-ie-and-chrome-browsers/)
 *  [Garth Gutenberg](https://wordpress.org/support/users/dosboy/)
 * (@dosboy)
 * [15 years, 5 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-problems-with-ie-and-chrome-browsers/#post-1791062)
 * Chrome 10.0.612.3 dev fixes the problem (just auto-updated).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SyntaxHighlighter Evolved] [Plugin: SyntaxHighlighter Evolved] Problems with IE and Chrome Browsers](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-problems-with-ie-and-chrome-browsers/)
 *  [Garth Gutenberg](https://wordpress.org/support/users/dosboy/)
 * (@dosboy)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-problems-with-ie-and-chrome-browsers/#post-1791059)
 * Thanks for the confirmation Alex. I thought I was losing my mind.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[SyntaxHighlighter Evolved] [Plugin: SyntaxHighlighter Evolved] Problems with IE and Chrome Browsers](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-problems-with-ie-and-chrome-browsers/)
 *  [Garth Gutenberg](https://wordpress.org/support/users/dosboy/)
 * (@dosboy)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-problems-with-ie-and-chrome-browsers/#post-1791057)
 * Same problem here (Chrome anyway, not tested in IE). Chrome’s console is throwing
   the following errors:
 *     ```
       Uncaught SyntaxError: Invalid regular expression: /\w+:\/\/[\w-.\/?%&=:@;]*/: Invalid character range
       shBrushBash.js:52Uncaught TypeError: Cannot read property 'Highlighter' of undefined
       shBrushJScript.js:45Uncaught TypeError: Cannot read property 'Highlighter' of undefined
       shBrushPhp.js:81Uncaught TypeError: Cannot read property 'Highlighter' of undefined
       shBrushXml.js:62Uncaught TypeError: Cannot read property 'Highlighter' of undefined
       shBrushRuby.js:48Uncaught TypeError: Cannot read property 'Highlighter' of undefined
       http://grinninggecko.com/ :456Uncaught TypeError: Cannot read property 'config' of undefined
       ```
   
 * I’ve tried disabling all plugins and the errors persist. Running Twenty Ten theme
   as well, so it’s a pretty vanilla setup.
 * Running Chrome 10.0.612.1 dev. The strange thing is that I just checked my version
   a few days ago and it was 9.0.597.19 dev – and I’m pretty sure it was working
   then. So it looks like the browser update broke something.

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