Jump to:
| Project: | Wysiwyg syntaxhighlighter integration |
| Version: | 6.x-1.2 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
I have the following modules and plugins installed and configured:
Wysiwyg 6.x-2.0
TinyMCE 3.2.6
Wysiwyg Pre Element Fix 6.x-1.0-beta1
Syntax Highlighter 6.x-1.20
Wysiwyg SyntaxHighlighter 6.x-1.2
Syntax Highlighter Plugin 2.1.364
TinyMCE is in working order. I have enabled all modules/buttons/wysiwyg profiles to allow for adding syntax highlighted code when using TinyMCE. However, the only way that syntax highlighting works is if I both turn on legacy support and use ... . This happens whether or not I've enabled legacy mode.
When trying to use {syntaxhighlighter brush ...} ... {/syntaxhighlighter} the saved text is just printed out verbatim. I've been able to set this up on another drupal site, but though perhaps I'm missing some key setup button (what a surprise...) that I've forgotten about, or perhaps there's something not quite right with the version mix I'm using... I've attached an image that illustrates the output. At the top of the image, you can see the result of wrapping source code with the , and at the bottom, the default {} macro wrapping.
| Attachment | Size |
|---|---|
| example_of_syntax_highligther_behavior.png | 67.89 KB |
Comments
#1
pre tags got filtered out in my post... it should read:
"...if I both turn on legacy support and use <pre class="brush ... "> ... <pre>."
...
"...you can see the result of wrapping source code with the <pre class="brush ... "> ... <pre>, and at the bottom..."
#2
have you enable the 'syntaxhighlighter' filter in you input format? Go to 'admin/settings/filters', click 'Configure' on your input format, make sure 'Syntax highlighter' is check.
#3
I'm having the same problem, and yes I have turned on the syntax highlighting. I've tried various combinations of everything with no success... and it seems the developer is AWOL. Its times like this I wish I was a little better with Drupal and PHP so I could track the fault down myself - but it seems to be the macro detection thats failing... it works fine using the PRE tags.
Any ideas... anyone?
#4
do you have a demo site that has the problem? If you give me access I'll poke around on the site for you. Otherwise, I have been unable to reproduce this.