Closed (cannot reproduce)
Project:
GeSHi Filter for syntax highlighting
Version:
6.x-1.1
Component:
Filtering
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2008 at 08:03 UTC
Updated:
22 Jun 2011 at 23:16 UTC
Comments
Comment #1
inteja commentedI'd still like to be able to do the above, but for the time being I am doing the code highlighting by calling geshi from directly within the contemplate (i.e. not relying on the drupal geshifilter module).
Comment #2
soxofaan commentedWhat does "nothing happens" mean? What do you expect? What do you get?
I'm not very familiar with Contemplate, so please elaborate a bit on that.
Comment #3
inteja commentedBy "nothing happens" I mean exactly that. No geshi syntax highlighting. No php errors. Just the raw, unadorned node content output.
Contemplate allows creators of CCK (and in fact any) node types to have unlimited control over how their nodes are displayed. You decide what is displayed and structure the output using PHP. Typically Contemplate exposes node attributes and fields like so:
In my contemplate, I take all my separate CCK fields (each of which represents an API class, method or variable), format them into an API interface and wrap them in a code tag with language attribute (to trigger geshi filtering), however the geshi filter seems not to work with this. I assume this is because drupal filters must be run before contemplate gets hold of the output, and then by me using the exposed variables above to access the raw content I am essentially bypassing any filtered content. If, on the other hand someone were to put a code snippet into one CCK field and wrap it with code tags and language attribute, I'm sure that would work as expected.
No matter, as using geshi.php directly in this case seems to work fine. It is just impossible to control via the geshifilter module administrative interface. I must do it in code within the contemplate itself e.g.
Comment #4
boombatower commentedPlease reopen if still relevant.