You can use xhtml while using textile, but you need to take into account that you are using textile. Which is to say: if you leave a blank line, textile is going to start a new paragraph for you…

For those who aren’t familiar with authoring WordPress plugins, you can easily alter the main textile() function [which WordPress calls for rendering text into textile output] so that it will not take action unless the post being displayed has a custom field value specifying to do so.

Simply replace the textile() function inside textileWrapperForWordPress.php with the following code block. Then, for the posts you want to be rendered with textile, you’ll need a custom field named “mime_type” that has the value of “textile” and viola, you’ve got textile output for that post only and your other posts aren’t affected.

function textile( $string=’‘ ) {
global $post;
$mime = get_post_meta($post->ID, ‘mime_type’, true);

if (isset($mime) && $mime == ‘textile’) :
$textile = new Textile;
return $textile->TextileThis($string, false, false, false, false);
else :
return $string;
endif;
}

sorty, meant to say Textile Rules!!!!!!!!

Submitting the original comment works fine, and they work fine in posts — it’s only when editing a comment that this seems to happen.

Can you advise us whether this is a bug in WP or in Textile 2.6 Beta?

(ext)This link

Textile 2.6 seems to recognize classes on spans and block-level elements only. Is there any way I can get it to recognize classes on my links? Thanks for your help.