Seeing me freak out at solving maths equations, my mom used to say that solving maths problems is fun once you get the hang of it. I thought that she’s just telling me that to finish up my homework, but I now understand because its not that solving maths has become fun for me but I’ve found coding & solving problems in there to be fun, which apparently some people don’t. So logically speaking, when you get going in something, it starts looking fun to you, whatever it maybe, be it solving maths problems or logical equations while coding or cooking!!
But then since I’m into coding & this blog is about that, so lets stick to that, and while we are at it, I would like to announce the v3.5 of iG:Syntax Hiliter. This version is an update to the v3.1.1 and has bugfixes and new features and the new GeSHi engine(v1.0.7.6) and two new languages, Ruby and MySQL. While the Ruby language file was created by me, I’ve included the MySQL language file from the GeSHi package to allow for hiliting of MySQL specific SQL. But then, as you should know, since v3.0 you are no longer bound to the language files included with the plugin, you can use any language file supported by the GeSHi version bundled with the plugin. So what’s new in this release, some of you might ask & here’s what I’ve to say:
- Tested for compatability with both WP1.5.2 and WP2.0.1
- You can use any other BB tag based plugin with iG:Syntax Hiliter now. A check is done for the existence of the language file in the appropriate directory and if the language file is not present there, the code is returned as it is with the tags, no parsing done on it.
- Code posted in the comments can be hilited using the appropriate code tags. However this feature can be enabled/disabled from the admin interface of iG:Syntax Hiliter.
- A colour picker is now available for you to pick colours of the line numbers displayed with your code.
- A new type of “Plain Text” view of code is available that gives you the plain text code within the code box itself.
That’s apparently not all. There was a bug reported where the “C” language’s code was not being hilited & its been squashed. For full details, please refer to the Manual, its not very much but it has some details. π
So without any further ado, download iG:Syntax Hiliter v3.5. Any bugs etc. that you may find or have anything to say about the plugin, please leave a comment here or on the official thread at the WordPress support forums at http://wordpress.org/support/topic/10533.
Colourful Coding to you all!! π
UPDATE:- The new “Plain Text” view of displaying plain text code in the codebox itself is kinda experimental. It has one known problem of the codebox getting resized to a small height making it impossible to view the code if it contains 1-2 lines of code. This is being looked into, so if you have a problem with this, please don’t report it as a bug. Patience is a virtue. You can report anything else that’s not already reported!! π
UPDATE:- The thread at WordPress forums seems to have been closed by the moderators there!! I don’t know why since I’m quite infrequent at the forums there now, so all questions etc. regarding the plugin go here. π
ah yes, that was an oversight, I know. this will be corrected in the next release & you’ll just have a directory which you’ll have to drop in the plugin’s folder. π
hello, iΓ’β¬β’m install plugin iG-Syntax Hiliter, iΓ’β¬β’m active the plugin and have error my blog
Warning: main(/home/percy/public_html/b9/wp-content/plugins/ig_syntax_hilite/geshi.php/wp-content/plugins/ig_syntax_hilite): failed to open stream: No such file or directory in /home/percy/public_html/b9/wp-content/plugins/ig_syntax hiliter plugin/syntax_hilite.php on line 31
Fatal error: main(): Failed opening required Γ’β¬Λ/home/percy/public_html/b9/wp-content/plugins/ig_syntax_hilite/geshi.php/wp-content/plugins/ig_syntax_hiliteΓ’β¬β’ (include_path=Γ’β¬β’.:/usr/lib/php:/usr/local/lib/phpΓ’β¬β’) in /home/percy/public_html/b9/wp-content/plugins/ig_syntax hiliter plugin/syntax_hilite.php on line 31
help me please..
Same issue as mine. From your wp-content/plugin directory:
mv ‘ig_syntax hiliter/ig_syntax_hilite’ .
Amit, I think you’d better solve this issue real soon π
C’mon guys, we are talking about a plugin used by programmers etc. & you are behaving like a bunch of newbies who are unable to install a plugin or unable to follow instructions written in plain english!! π π
Eh eh eh! It’s not our fault :-D… your instructions should have been more appealing π
Hey! Thanks for this! Is terrific.
I am curious, though, if there is a set of tags for “command prompt” usage ? For example, I want to write out instructions from the linux command line or the Mac terminal. Anything to add to make that happen ? Or just use plain [code] ? Thanks again!
Damon
Damon, check out the GeSHi website for the language file that you seek!! π
Congrats man for this great plugin, I really need it for my blog, it’s really useful to highlite the linux commands.
Thanks again and keep up the great job!!!
I just wanted to clarify my above posting – iG:Syntax Hiliter is a great plugin and the installation is easy – it has many configurable options and is a great choice for your code highlighting needs! Thanks for the plugin and keep up the great work!!!
I have the same problem as Cody.The setting will be lost when changing plugins.My wordpress version is 2.0.5.
and Gythialy, you have the latest version of plugin??
Yes,My version is 3.5.
Hmm, I haven’t had time to look at this in last few months, but rest assured that this will be tackled when I start working on the next release which is sort of due now. For now, please accept my apologies. π
It’s a very good plugin, hope the next version will be prefect.^_^
hi, i’m a happy user of your iG:Syntax Hiliter plugin until recently i found out that the keyword group url created by GeSHi will have an extra tag behind it, this make mu blog not xhtml valid anymore. i dun think it’s ur plugin problem, but i would like to know how to disable the keyword group link.
however i found out from GeSHi documentation that to disable keyword group url i only need to put
[php]
$geshi->set_url_for_keyword_group($group, ”);
[/php]
but may i know where should i put that in ur plugin?
thanks π
Yeah, the extra tag is not plugin’s problem. In the plugin file “syntax_hilite.php”, you can put that line to disable the group URL after line 138 which is:
[php]
$geshi->set_header_type(GESHI_HEADER_DIV);
[/php]
but make sure its outside the line number “if” statement:
[php]
if(IG_LINE_NUMBERS) {
[/php]
That should remove the keyword links. Also, you can manually remove them from the language files as well.
hi, thanks for your reply, i tried what u said and put the following line
[php]
$geshi->set_url_for_keyword_group($mType, ”);
[/php]
in between the two line you mentioned, but seems nothing happen. π
Hmm, well, maybe this function is not available for the GeSHi v1.0.7.6 which came with the last version of plugin. You should open your language file(s) & remove the keyword URLs yourself. But remember to backup your language file(s) before you do it.
too bad π for now i just comment out the url function in GeSHi.php instead of removing the url in each of my languange file. anyway thanks for ur suggestions, hope the next release will be better, and keep up the good work π
Hi there and congrats to that superneat plugin.
I think I’ve found a minor bug in it though.
When typing a less-than condition, the blank space behind the less-than sign gets stripped out.
[as]
if (gna < blabla) { trace('cheers'); } [/as]
hi,
i using this plugin but not working on my blog.
wp installed differen directory “site.com/wp/”
i change
$igsyntax_hiliter_path = get_settings(‘siteurl’).”/wp-content/plugins/ig_syntax_hilite”;
get_settings(‘siteurl’) or get_settings(‘site.com’) none not working.
help me please. thanks
hi again π
$igsyntax_hiliter_path = get_settings(‘siteurl’).”/wp-content/plugins/ig_syntax_hilite”;
“siteurl” working
thanks π
i got problems since the new wordpress 2.1
the highlighter escapes to much eg. this code line:
$encoder->get_crypt_source();
results in:
$encoder->get_crypt_source();