Worming my Way Out!!

Leave a Reply

Comment as a guest.

  1. 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!.

  2. 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.

  3. 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!! ๐Ÿ™‚

  4. 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…

  5. Pingback: blog-j
  6. 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!

  7. 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. ๐Ÿ™‚

  8. 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!!

  9. Hi, I just ugpraded to 3.1.1 from 2.01. I get “cannot modify header information” error.

    Warning: Cannot modify header information – headers already sent by (output started at /home/liewcf/public_html/blog/wp-content/plugins/syntax_hilite.php:1) in /home/liewcf/public_html/blog/wp-admin/admin.php on line 10

    Warning: Cannot modify header information – headers already sent by (output started at /home/liewcf/public_html/blog/wp-content/plugins/syntax_hilite.php:1) in /home/liewcf/public_html/blog/wp-admin/admin.php on line 11

    Warning: Cannot modify header information – headers already sent by (output started at /home/liewcf/public_html/blog/wp-content/plugins/syntax_hilite.php:1) in /home/liewcf/public_html/blog/wp-admin/admin.php on line 12

    Warning: Cannot modify header information – headers already sent by (output started at /home/liewcf/public_html/blog/wp-content/plugins/syntax_hilite.php:1) in /home/liewcf/public_html/blog/wp-admin/admin.php on line 13

    Any idea how to solve it?

  10. 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!!

  11. ร‹โ„ข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?

  12. 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.

  13. uruloki: I tried the previous version 3.0 annd everything works fine. Maybe you want to try the previous version too?

  14. 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).

Sliding Sidebar