Comments on: WordPress Plugin – Textile 2.0

By: Jaykul

Jaykul — Sun, 11 Jan 2009 04:26:27 +0000

I use WPSuperCache, and haven't had any problems with the site lagging with changes, as far as I know ... honestly, I don't have any problem with the concept of storing both copies.

When I wrote this I couldn't think of a way to store the two copies and have the front end show one version and the back end show the other. I can think of a way now... maybe I'll recode it after all

By: ikaruga

ikaruga — Sun, 11 Jan 2009 03:38:07 +0000

I don't see anything wrong with storing two files — memory is cheap, speed and performance, on the other hand, are not. (Ex: my host gives me unlimited storage but temporarily takes me down if my site overwhelms their servers. In any case, we're talking about text files, so storing a second copy is not significant.)

The real problem Joel is dynamically creating the html each time someone visits a page. That slows down your site (specially on a cheap host). Plus, if you ever get any decent traffic (say from digg), that'll kill you…

I'm not really familiar with the cache plugins on wordpress —- but if I recall correctly, (at least on drupal), you don't enable them all the time because your site lags with changes you make. That's why the drupal textile plugin keeps a cache copy of the html. The result is that regardless of whether or not the cache is enabled, textile does NOT slow down your site…

By: Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Thu, 18 Dec 2008 05:21:07 +0000

It does not cache the output � there are already many plugins for caching full WordPress pages, and having the Textile plugin cache it�s output separately would mean storing two full copies of the article (in each markup: Textile and Html) so that you could edit it � because nobody�s ever gotten Html->to->Textile conversion working satisfactorily.

By: ikaruga

ikaruga — Wed, 17 Dec 2008 05:53:28 +0000

Hey Joel, does this plugin store a cache version of the HTML. Or does it convert the textile page to HTML on the fly each time someone visits the page?

By: Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Fri, 12 Dec 2008 19:01:10 +0000

It does not cache the output — there are already many plugins for caching full WordPress pages, and having the Textile plugin cache it’s output separately would mean storing two full copies of the article (in each markup: Textile and Html) so that you could edit it — because nobody’s ever gotten Html->to->Textile conversion working satisfactorily.

By: ikaruga

ikaruga — Fri, 12 Dec 2008 04:21:09 +0000

Great plugin I love textile! Hey, so performance-wise how does this fare? Is a cached version of the html stored in the database or is it generated each time someone visits the article?

By: Simon Wakeman » Making the move to Wordpress

Simon Wakeman » Making the move to Wordpress — Tue, 25 Jul 2006 05:34:24 +0000

[...] Migrating content over from Textpattern was as simple as running a built-in script, which moved the content without any errors. The template migration was quite straightforward – I merged the XHTML/CSS from my old Textpattern templates with code taken from the great Minimalist Sandbox template. I then went through all my old content and removed the Textile (although had I wanted to continue with Textile there’s a plug-in available to run Textile in WordPress). [...]

By: Jaykul

Jaykul — Sun, 26 Mar 2006 21:31:20 +0000

I see what you mean … I think you will find that none of the attributes work on links in Textile at all (test here). Which is to say: this is not a problem with my plugin, which is merely a wrapper, it’s the way the Textile parser works. I am not usually prepared to alter the parser, since IMHO, these pseudo-markup languages are only useful when they work the same way everywhere…

PLEASE feel free to file bug reports:
http://www.textism.com/tools/textile/index.php

By: Jon Zuck

Jon Zuck — Sun, 26 Mar 2006 19:29:22 +0000

Jaykul, Tom is right. The plugin is not parsing class attributes correctly. “link text(oop)” would give a TITLE attribute of “oops.” Parentheses coming before the text should give a CLASS of “oops.”

I assign an “ext” class to all my external links. The parser bug is most frustrating.

By: Jaykul

Jaykul — Thu, 23 Mar 2006 02:42:38 +0000

I think you mean to put “link text(oops)” which works like: link text