akarmenia

Hmm, I’m not really sure then. It may be your theme or other plugins that might change the content around with Crayon, I’m not sure without having access to all that.

I have 100MB of memory and PHP 5.2.11, but anything 5+ should do it.

I’m afraid I can’t manage to reproduce your problem, it works fine for me:

https://aksandbox.webege.com/?p=76

Ah I see. I’ll look into it and get back to you.

Hmm, can you confirm if it works on version 1.7.30? I don’t think I changed anything that would affect the load sequence in such a way as to totally halt the script. The filter the_posts should be called after init, but there is no sign of it. This indicates that something is not working correctly, since the Crayon id is added to the content after the_posts should reach the log. Could you please provide the name of the theme you’re using?

Try this:

https://dl.dropbox.com/u/33811812/Crayon/crayon-syntax-highlighter-1.8.0-debug.zip

I’ve enabled debugging. Clear your log in settings, then refresh the problematic page and then send me the log, either from settings or the log.txt from FTP.

Hmm, very odd. That’s the id that Crayon adds to differentiate between other instances (for js). I’ll look into it. Can you confirm if this works on the default theme?

Yep, added it to the list of Planned Features. Should be there soon, I’ll update here when it is.

Cheers, see 1.7.23 for the font changes.

Thanks for the suggestion. The reason I had import was because themes can import their own, which must be specified in the theme css, but what I plan on doing now is to remove the theme-default font and set it to Monaco, then to remove these imports and let the use choose whatever font they want. Then, it will enqueue Monaco or whatever other chosen font there is. I’ll try to finish this tomorrow.

?? good to hear it’s working, I also got rid of the <br /> tags

I think it was fixed, either way, fixed some more stuff in 1.7.19 ??

Any luck?

Try this: https://dl.dropbox.com/u/33811812/Crayon/crayon-syntax-highlighter-1.7.18-beta.zip

You’re right, I became aware of this issue recently and I’ve decided to fix it now that you made me aware of this space. I knew the <p> tags were being cut short by a <div>, but I didn’t realise the browser would try to fix this by closing it.

https://stackoverflow.com/questions/8950684/regex-detect-text-that-exists-between-p-p