Code for Fun!!

Leave a Reply to Amit Cancel Reply

Comment as a guest.

  1. I tried it with WordPress 2.1.3 and it make wordpress shut down (white screen only).
    I have used your plugin heavily on my website and now can not upgrade.
    When can one expect a compatible version of your plugin? Or do I have to check some error I could have done?

    Matthias

  2. Matthias, I haven’t had time so far to even try the plugin & see if it works with new WP or not. I’ll soon do so, but in the meanwhile please do look on your side that you’ve not made a mistake somewhere since mistakes can happen. 🙂

  3. I love this plugin, but the “Show Plain Text Code Option” infrequently resetting itself to “YES” kind of drives me nuts 🙂
    (WP 2.1.3, latest plugin download)

  4. Umm yeah, have had that complaint for sometime now & am umm, sorry to admit that I really haven’t had time to even look into the plugin yet, been busy with personal & professional life. But an update will be out soon, I promise. 🙂

  5. Great to see you’ll be updating the plugin some day, Amit 🙂 One feature request then : disable the stuff that parses code to put a link on every function found (ie “echo” replaced by the link to function echo on php.net)

  6. Hi!

    At first, thanks for a good work. We are using this plugin in our blog to get the code highlighted. So far, so good 🙂

    Today I ran into problems and found some very nasty bugs. XML highlight doesn’t ork as expected. If I use namespace prefixes then instead of prf:Title I get prf :Title. Also I found no way how to make ASP.NET tags to work without problems. XML tags with prefixes are working normally in Geshi – I tried out on their online syntax highlighter.

    May be you can add those fixes in next release?

  7. Today I ran into problems and found some very nasty bugs. XML highlight doesn’t ork as expected. If I use namespace prefixes then instead of prf:Title I get prf :Title.

    Ain’t any bug in the plugin, highlighting problems should be directed to GeSHi website & Nigel(its developer).

    Also I found no way how to make ASP.NET tags to work without problems. XML tags with prefixes are working normally in Geshi – I tried out on their online syntax highlighter.

    It doesn’t support ASP.NET(the current plugin release & the GeSHi bundled with it). It has support for VB.NET & C# though. Besides, if you see the date of this post(just about the date when this plugin was released), it should tell you that its of Feb. last year & GeSHi has had some releases after that, so the plugin hasn’t been updated really! I’ll release an update soon, but really can’t say when. 🙂

  8. I’m having problems where are being changed to & lt ; and & gt ; (without the spaces of course) when I view my posts, but they look fine in the editor My guess is it has something to do with being wrapped in the tags. Any suggestions?

  9. Ryan, have you tried to see your post without using the tags? See how your code is displayed, if its converted to html entities or not.

    Cornelis, there’s no such option to display plain text by default or only plain text, since that is rendered by Javascript.

  10. Yes, it shows up as the HTML entities in the source code. And I assume that’s the correct thing for it to be doing since I need to be able to enter HTML tags without them acting as HTML tags. But they’re HTML entities in both the Geshi and plain text views and in plain text they show correctly, but the entity code is displayed in the highlighted version.

    Here’s an example page. Line three has a couple of in it that display as entities in the highlighted view but display as the correct character on the plain text view.

  11. A little more information. I’m using version 3.5 of your great plugin. The blog that’s having issues is WordPress 2.2. I have the same plugin, same version, installed on a WordPress blog version 2.0.3 and it works fine.

  12. Ok, I’m answering my own questions 🙂 It has something to do with the HTML editor. If I type the code in the Code tab it works, if I type it in the Visual tab it gets messed up. My guess is that the HTML editor is converting to entities and maybe Geshi is too so they’re confusing each other. Either way it’s sort of working.

  13. Ryan, it seems to be alright to me.

    It has something to do with the HTML editor. If I type the code in the Code tab it works, if I type it in the Visual tab it gets messed up. My guess is that the HTML editor is converting to entities and maybe Geshi is too so they’re confusing each other.

    Did you read the plugin manual? If you did then you wouldn’t have posted for help here, because in the manual its very prominently written that your code won’t mix well with the WYSIWYG editor & hence might not get displayed correctly, in which case there’s nothing that I can do, so its hardly good to post here that it ain’t working!! 🙂

  14. Crap. If it was that much of an inconvenience delete my messages. Sorry to have been a burden. Most software authors I’ve come across are more than willing to help. Guess that’s not true for everyone.

  15. Dude, you took it in the wrong sense. what actually I meant was that the manual provided in the package is there for a reason. had you read it, you would’ve saved yours & my time. But by your snobbish attitude, I can only imagine that you take it as if I or other people have any obligation towards you by which you should be provided support! For your type I simply have to say that since you didn’t pay for this software or support, it would be better if you be polite & understanding. I didn’t refuse to help you out, nor am I doing it now, but if the manual/help/instructions are provided in a package, you should read them.

    Its not expected from non-techie users, but since you are using my plugin, I assume you are a techie & atleast a techie can bother to read instructions before banging on the developer’s door telling him something’s not working!

    Rest is up to you, be snobbish or polite, hardly matters to me! 🙂

  16. My apologies, tone doesn’t come across very well typed out. I do appreciate the plugin, and I really have read the manual twice, once each time I’ve installed it on a blog. Maybe the warning about WYSIWYG could be up in the installation section rather than at the very end.

  17. My apologies, tone doesn’t come across very well typed out.

    Yeah well, thats why I used a smiley. Anyways, apology accepted! 😉

    I really have read the manual twice, once each time I’ve installed it on a blog. Maybe the warning about WYSIWYG could be up in the installation section rather than at the very end.

    Its mentioned under the Important section, for the obvious reasons! 😉

Sliding Sidebar