Yes, a bug was reported in iG:Syntax Hiliter v3.0 that can stop the plugin from working, or in other words, can break your plugin and the post. This was due to the fact that a new RegEx was used for the tag parsing and I uh well…………..
So, if you used any square brackets like [ ] in your post, well, you can understand…………..
So here’s critical bug fix, iG:Syntax Hiliter v3.1 with not only this, but another minor bug fixed and some other bugs that I came across, including a bug fix in GeSHi. I’ve sent the fixed GeSHi to Nigel and hopefully it’ll be officially patched in its next release. But for now, you need to use the geshi.php provided with this plugin!! Also the language files bundled with iG:Syntax Hiliter have been updated with some style modifications, so essentially, you should make this a clean install, updating all files. ๐
So without further ado, please download iG:Syntax Hiliter v3.1, its a must update for users of v3.0 and ofcourse a most recommended update for v2.1 or lower(only if you are using WordPress 1.5 or above). ๐
As always, bugs/complaints/suggestions are welcome here or at the WP Support thread at http://wordpress.org/support/10/10533/ or you can Contact Me(please mention iG:Syntax Hiliter as the subject).
UPDATE: A more generic fix has been applied to remove the whitespace between the opening tag brace(<) and the first character of the tag, which is placed by WordPress. If you don’t display any code except that of PHP, JSP, ASP or RubyOnRails, then you won’t need it, but if you display any other tag based code, like ColdFusion, Blogger or MovableType template tags etc, then this fix is a must for you unless you prefer broken tags.
Please download the plugin again for the latest version.
IMPORTANT: iG:Syntax Hiliter doesn’t change or fix your code in anyway, it simply manipulates it a bit for on screen display. Your code remains saved in the same form as it was saved by you.
Its glad to see you have repaired these bugsรฃโฌโThanks for your great work. I has upgraded it to 3.1.
keep it up!
Thanks!.
Because of the javascript line added to the head section the validator didn’t want to validate the page: saying the “type” is missing. So in the syntax_hilite.php I added to line 180 this:
type="text/javascript"– and now it’s OK.Moshu, that’s good. ๐ However I don’t follow the Validation religiously!! ๐
I just modify your plugin a bit to enable it on comment. You can test it here: http://www.phpvietnam.net/blog/index.php/archives/2005/07/09/enable-ig-syntax-hiliter-on-comment/
Thanks for excellent work
That’s good pcdinh. Comment code hiliting will be available in the next version, with a twist though!! ๐
Hello!
Having a little problem… How does indentation works? I put spaces on my post between igsyntax tags but they don’t show up on the post…
You can see it here:
http://www.inerciasensorial.com.br/2005/09/03/php/introducao-ao-ajax/
where did you put spaces in your code? because its wierd since it works even if you indent your code with just 1 whitespace character!!
I use tabs in my code, that is, I write my code in a text editor & indent it with tabs & then copy it in my posts, the tabs are then automatically converted to 4 whitespace characters.
If that still doesn’t solve your problem then you can email me your WP username/password and I can look into it!! ๐
Hi there, as I installed this plugin I saw that it takes over my phpbb tags, so I cant use them anymore… For example if I write [URL]http//…[/URL] it shows me URL as script name and the http//… as the code…. Is there a way to limit Hiliter functionality, I mean that it’d used only the tags that it needs…
Hey Amit ๐
Remember me, the guy with indentation problems? Well, I found out what it is ๐
I am using another plug-in called IImage Gallery (which rocks btw), and the plug-in trim()s the post content, line by line! So, WordPress applies IImage and pass its generated text to IG Highlighter, which gets nothing to indent :p
I commented the line with the trim() and my site still seems to work fine, so I will leave it that way for now ๐
Cya!
Julio, what you can do is set the Image Gallery plugin to run after iG:Syntax Hiliter. Like on the plugin’s line #398, there’s an add_filter() call. There will be a similar add_filter() call in that ImageGallery plugin, find it & set the number in the last parameter(3 & 4 in iG:Syntax Hiliter) to be higher than 4(5 will do). This will cause the ImageGallery plugin to load after iG:Syntax Hiliter and by then, iG:Syntax Hiliter would have the spaces converted to HTML entities which ImageGallery won’t be able to trim, thus preserving your indentation. ๐
But I would test around with it as ImageGallery plugin might be doing something that requires it to load earlier. If I were you, I’d ask its developer about it rather than playing blind, but if you know & understand the ImageGallery plugin’s code, then its ok. ๐
F**k you B***h, why delete my comment, you d**k head!
Apparently I’m not interested in providing any help to someone who uses a false email like nospam@nospam.com & a false domain like http://www.domain.com & probably a false name as well. If you don’t want to provide your email & domain, then don’t provide it, but you’ve no right to insult me by providing any false information like that!!
And this childish behaviour of yours by posting a comment like this just shows background as to how cheap it is, & for showing such cheap attitude, you’ve just got yourself banned from here!! Don’t darken my blog again with your dirty shadow!!
Hi, I just ugpraded to 3.1.1 from 2.01. I get “cannot modify header information” error.
Any idea how to solve it?
did you open the plugin file in a text/code editor or IDE before uploading it to your website? this error usually comes when there are spaces/linebreaks after the closing PHP delimiter(?>) at the end of the file.
Try this:
Open the file in a text editor that supports UTF8 & save the file as UTF8 without modifying anything. Make sure that there are no spaces or linebreaks after the last PHP closing delimiter(?>) in the plugin file.
This should solve your problem!! ๐
Post here if it works!!
รโขthank you for promptly reply. I actually unzip and upload it straight away. I did not modify it. Aynway, I try to save in UTF8 and upload but still the same error.
May I get the previous version(example: 2.x) to test if it works?
Hello,
I am getting the same error as commenter LcF above. Like him, I unzipped and uploaded straight away. I did check on the EOF (using VisualStudio) and did not have any spaces or linebreaks.
Any help would be appreciated.
uruloki: I tried the previous version 3.0 annd everything works fine. Maybe you want to try the previous version too?
I’ll go ahead and use 3.0, hopefully I remember to not use any [….
Thanks LcF!
uruloki, have you tried the suggestions I gave in my last comment(posted above)? I suggested these same things to the other 2 people & they had the plugin going right for them, only LcF has had problem with them(& thus he has to use v3.0).