On 7/6/06, Scott Laird <[EMAIL PROTECTED]> wrote: > Can you try something for me? Edit > components/plugins/textfilters/textile_controller.rb and > change RedCloth.new to RedCloth::Textile.new. Then tell Typo to rebuild all > of your cached HTML and see what happens. It should fix your problem.
That didn't work for me; instead, it removed all formatting from entries. Using irb to try this I get "uninitialized constant RedCloth::Textile.new". This, however, does work: RedCloth.new(text).to_html(:textile) > Now, should this fix go into the trunk or not? It'll change long-standing > behavior, and may break some people's formatting. It's a bug, but it's an > *old* bug. Opinions? As a new user, I can tell you I was surprised to find this happening -- and it didn't happen when I was running the stable-2.6-with-frozen-Rails release. Which, on looking, used code very similar to my fix, above, to render textile: txt = RedCloth.new(txt, restrictions).to_html(:textile) I vote "yeah, it should go in, with an option to apply both Textile and Markdown for those who want it". _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
