Forum: Radiant CMS enkodertags extension problem

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Ff2c500b4f2690c6e60d580f6b3caf78?d=identicon&s=25 David Minor (Guest)
on 2007-05-19 18:54
(Received via mailing list)
I ran into a problem yesterday with the enkodertags extension not
displaying properly and I meant to post to the list, but instead I
inadvertently emailed Sean Santry directly.  He was quick to help and
pointed out that the textile filter was probably endcoding the html
created by the tag.  I wanted to share my solution here and ask a
question to further both my knowledge of radiant's structure and
offer a fix for Sean's extension.  I'll post my email with Sean in
it's entirety below.

The fix as of now is to wrap the enkoder tag with
<notextile><r:enkoder_mailto ... /></notextile> in my page part.
What immediately jumped out at me is that enkodertags should be
looking for the textile filter and adding the <notextile> tags
itself.  it would happen at the very end of the enkode_it method just
before the result is passed back.  The question is, what to check
for?  Can I check for the filter type of the page part or snippet
from within the Enkoder object?

Here's the original post that should have come to the list.  Thanks
for the help Sean.
Ff2c500b4f2690c6e60d580f6b3caf78?d=identicon&s=25 David Minor (Guest)
on 2007-05-23 06:15
(Received via mailing list)
is the page part's filter status available to a tag in an extension
called from that page part?
This topic is locked and can not be replied to.