Comments on: Fix for “Leading Whitespace Bug” in Syntaxhighlighter Evolved for WordPress

By: Nick

Nick — Wed, 11 Jan 2012 11:54:03 +0000

Thanks a lot. I used your tutorial to fix ‘chrome-auto-translate-plugin-dialog’ divs that are inserted automatically in tinyMCE.

By: Abel Braaksma

Abel Braaksma — Sun, 06 Sep 2009 12:49:51 +0000

@DOHAB: I noticed that using a plugin like the Excerpts plugin causes this behavior: when you edit an excerpt, even outside your original post, it re-saves your post, but also re-escapes all HTML entities, resulting in incorrect data. It is possible that you use a similar plugin with similar issues. Try disabling plugins one by one to find out what's causing this and then take it on with the author of that plugin.

By: Dohab

Dohab — Sat, 05 Sep 2009 19:49:13 +0000

that’s strage!
I just created a post and test the same code and it works just fine. wth’s goinon??

By: Dohab

Dohab — Sat, 05 Sep 2009 19:28:14 +0000

the code fix it self here, but not in my case.

By: Dohab

Dohab — Sat, 05 Sep 2009 19:26:45 +0000

I’m still having this problem too, thus I’m using the latest version 2.2.1 (at the time i wrote this response) which says it has fixed, but it’s not, the bug still there.

I tried every fix I read about it too.

My code still looks like :

even qouts converted.

By: Jon Smith

Jon Smith — Thu, 23 Jul 2009 22:00:31 +0000

This is awesome. Thanks for your contribution. The whitespace problem is the only thing that has stopped me from using SyntaxHighligher Evolved.

By: Abel Braaksma

Abel Braaksma — Sun, 12 Jul 2009 14:33:33 +0000

Thanks for pointing that out, I expanded and abbreviated the section, hopefully it is more factual now.

Also thanks for bringing out a new version of the plugin which includes this fix. I’ll have a check at the copy-problem.

By: Abel Braaksma

Abel Braaksma — Sun, 12 Jul 2009 14:31:02 +0000

Hendrik, can you try to check whether you get any errors by following the instructions here? Note that it will not work with pages or blogs you already saved. The spaces are lost for these ones and have to be added again. Viper has meanwhile updated the plugin. To effectuate the bugfix, all you have to do now is go to your plugin repository and click Upgrade Automatically for the Syntaxhighlighter Evolved plugin: If that still doesn't solve your problem please let me know. -- Abel --

By: Viper007Bond

Viper007Bond — Sat, 11 Jul 2009 21:57:02 +0000

Your “Prologue” section is incorrect.

I wrote the original SyntaxHighlighter plugin. It was based on some code that Matt gave me that WordPress.com used at the time. I improved it significantly and mdawaffe contributed some great kses code.

Other people came along and wanted to add their own features to the plugin, so they forked it and poorly named their forks (Syntaxhighlighter Plus is one of those forks). I contributed no code to the “Plus” version, although it was based on my plugin.

Getting this confused is quite understandable though. The forkers chose very poor names.

By: Hendrik

Hendrik — Sat, 11 Jul 2009 00:45:31 +0000

I came across the same whitespace problem but your fix doesn’t work for me. I’m using WP 2.8, FF 3.5 and the latest version of the plugin. I already disabled and emptied my cache. Any ideas?