Huddled Masses - Latest Comments in Textile Plugin 2.6 released

Re: Textile Plugin 2.6 released

Jeremy Helms — Wed, 28 Mar 2007 01:37:45 -0000

bq. 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;
}

Re: Textile Plugin 2.6 released

Sat, 12 Aug 2006 01:25:16 -0000

Man! I love you!!! Textules!!!!!

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

Re: Textile Plugin 2.6 released

Rocky Davidson — Tue, 04 Jul 2006 13:50:56 -0000

I just installed textile. I guess I just don't get it. Nothing appears different in my editing box. What am I supposed to see. I have not found any installation instructions. Maybe I am missing something.

Re: Textile Plugin 2.6 released

Jon Boyd — Tue, 13 Jun 2006 18:02:48 -0000

I also have a problem, which I've noticed only since WP 2.0.3 (so it's easy to blame the upgrade): editing a comment with single quotes in it turns the single quotes into backslash-single-quotes. (That is, \' )

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?

Re: Textile Plugin 2.6 released

Jon Zuck — Sun, 11 Jun 2006 12:47:27 -0000

Disregard my last post... I got that problem fixed. I REALLY like Textile 2.6, but there's just one thing that's not working for me. I give my external links a class, e.g.

"(ext)This link":http://thislink.com

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.

Re: Textile Plugin 2.6 released

Jon Zuck — Sun, 11 Jun 2006 05:31:10 -0000

I'm having trouble with Textile plugins since I upgraded to WordPress 2.0.3. It seems all the plugins, (including 2.6) seem to start all posts with two beginning paragraph tags, and end with two closing p tags. This is driving me crazy. Am I doing something wrong? Please help. Thanks

Re: Textile Plugin 2.6 released

PA?l DegerstrA?m — Mon, 15 May 2006 17:35:16 -0000

@Jaykul: Thanks, I will.

Re: Textile Plugin 2.6 released

Matt — Sun, 14 May 2006 13:59:06 -0000

I installed your plugin - thanks, I love Textile2! I got fed up with the default WordPress editor because it kept messing up my pre tags, and now I'm glad I started looking for a replacement. This is a much more sensible way to create content than hand-coding HTML! :-)

Re: Textile Plugin 2.6 released

Paul — Sat, 13 May 2006 22:02:17 -0000

Thanks. I finally figured out that the marked up text that was showing up in the feed was coming from text in the WP2 "excerpt" entry area. I don't remember putting it there, but there it was anyway. I removed that (which as I understand was overriding what WP2 would normally provide the feed as a post excerpt) and things are back to normal. I agree with you about HTML not being in RSS. I was confused about where the markup was coming from and just figured that WP2 normally stripped the HTML out but didn't recognize the textile markup as such and left it alone. Anyway, thanks for the quick reply (and the plugin!) -- much appreciated.

Re: Textile Plugin 2.6 released

Jaykul — Sat, 13 May 2006 20:56:19 -0000

PA?l: You should probably submit that to the author of textile itself, through his testing and bug-reporting page, "here":http://www.textism.com/tools/textile/.

Paul: You *can* parse your feeds (I just don't think RSS should have HTML embedded in it). Just uncomment the next-to-last line in the plugin: @// add_filter('the_excerpt_rss', 'textile', 6);@ (that is, delete the slashes at the front so it just looks like: @add_filter('the_excerpt_rss', 'textile', 6);@).

Re: Textile Plugin 2.6 released

Paul — Sat, 13 May 2006 19:35:05 -0000

Questions: I started using the latest Textile 2 plugin and then started using FeedBurner so I could publish summaries of the weblog entries on another site. FeedBurner is including the Textile markup in the feed data. I'm guessing this is because WP 2 is responding to feed requests straight from the database so the markup never goes through the textile plugin to get converted on its way to FeedBurner. Is this right? If so, is there a way to fix it?

Re: Textile Plugin 2.6 released

PA?l DegerstrA?m — Sat, 13 May 2006 16:53:13 -0000

When doing this:

==
* "Some text":http://www.example.com
Text on a new line.
* "Some more text":http://www.foo.bar
More text on a new line
==

the list isn't closed (the last and are missing). It seems having text on a separate line (using double space after the link) breaks something. Is this something you can fix?

Thanks for a great plugin!

Re: Textile Plugin 2.6 released

Jim — Thu, 04 May 2006 15:20:48 -0000

left arrow, exclamation point, dash, dash from the left side and one dash from the right side of the quicktag, which essentially renders it useless. I had the same problem when testing it on the textism site. Dunno if it's something I'm doing wrong or a bug in the system.... Any help you can provide would be greatly appreciated. You can see what it's doing to my contact form here.

Re: Textile Plugin 2.6 released

Jim — Thu, 04 May 2006 15:11:38 -0000

Hmm, and I'm noticing that it did it here, as well - removed the

Re: Textile Plugin 2.6 released

Jim — Thu, 04 May 2006 15:06:48 -0000

I have a contact form plugin that I use. The plugin requires a quicktag (====) to be inserted into a page in order for the contact form to appear. When I upgraded from Textile1 to Textile2, my quicktags suddenly stopped working. I even turned Textile2 off for a moment to verify that it was, indeed, the thing that was breaking the quicktags. The nearest I can figure is that Textile sees the dashes before and after the quicktag and tries to convert them into formatted text.

Re: Textile Plugin 2.6 released

Jaykul — Thu, 04 May 2006 00:29:55 -0000

What on earth do you mean? The quicktags are just little javascripts that insert html tags. There's nothing in Textile that affects them ... in fact, I just tried it and they work fine. Or are you talking about tags in the COMMENTS? They're disabled by default, but you can see in the comments above how to to enable them again.

Re: Textile Plugin 2.6 released

Jim — Mon, 01 May 2006 13:41:29 -0000

I love this plugin, but I've discovered that this recent version breaks the WordPress ability to use quicktags. Do you have a workaround solution for this?

Re: Textile Plugin 2.6 released

Whisper — Tue, 18 Apr 2006 19:36:27 -0000

OK I hate being annoying but after very close look at the files (textile2b and geshi) I found out why it wasn't working.

In your textile2b file it says this around line 812:
@/* when using a code beautifire, we don't want this between code tags - Joel
NOTICE: this will (still) break if you use both: */
$offtags = ('pre.*|kbd.*|notextile');@

and in the geshi file (geshi.php) around line 116:
@ var $header_type = GESHI_HEADER_PRE; // The type of header to use@

That variable needs to be set to GESHI_HEADER_DIV *knocks self on head*
I can't believe how long it was staring at me. Geshi was putting pre inside the within code so it was breaking it. So yeah this will fix the problem for those that wanna use Geshi ;)

(BTW you can delete my previous posts I won't be offended and this little aside too :* )

Re: Textile Plugin 2.6 released

Whisper — Tue, 18 Apr 2006 16:56:51 -0000

I must sincerely appologize. It was not Textile at all that was messing with TinyMCE it was in fact another plugin. Apparently it took it a little while to kick in though __sigh__ . I am so sorry for my assumption. So the TinyMCE problem is solved ;) again I'm sorry.

Re: Textile Plugin 2.6 released

Whisper — Tue, 18 Apr 2006 14:49:09 -0000

I installed your plugin on one of my blogs that I share with some family members. After they played with it and decided they would rather just use the rich text editor I uninstalled it (deactivated it and deleted the file) Now I have a problem. The rich text editor is gone, everyone has the option enabled in their profile, it's also enabled on the Options page, but it will not load on the "Write" pages. I have looked everywhere I can think of even in the DB and cleared my cache folder too. I cannot find whats causing this and the last thing that happened right before it disappeared was the instalation of Textile. Can you help me please :)

BTW I do have this installed on MY blog and I *LOVE* it thank you so much. Though I wish I could get mine to work with Geshi like you did, but no biggie I would so rather have Textile than Geshi. Beautiful plugin now if only my family would understand how nice it is :P

Re: Textile Plugin 2.6 released

Arne — Sun, 26 Mar 2006 17:18:50 -0000

thx, commenting out these two lines did it for me :-)
@contact form plugin: well, i dont know anything about wp's plugin structure, so i dont know in which way i could change the plugin. i only can see that you're right: it's calling a filter for "the_content".

thats the plugin: http://johannesries.de/webwork/contactform/

Re: Textile Plugin 2.6 released

Jaykul — Sun, 26 Mar 2006 16:42:33 -0000

Jeremy: That's a good question. I'm not 100% sure if this will do what you want, but you can try using the 'lite' version... You will see on lines 992-995 the function @textile@ which calls @TextileThis@, and passes only one parameter. Make yourself a copy, call it @textileLite@ and change the call to @return $textile->TextileThis($string, true);@ ... then, in your @add_filter@ calls, use @textileLite@ instead of @textile@.

Arne: Look at the bottom of the file. Line 1008.
Arne: Contact form plugin? It must be (inappropriately) calling a filter for 'the_content', 'the_excerpt', or 'comment_text' ...

Re: Textile Plugin 2.6 released

Arne — Thu, 23 Mar 2006 13:23:19 -0000

and another problem here... the contact form plugin doesnt work, also because of textile. isnt there a notextile-tag like in txp?

Re: Textile Plugin 2.6 released

Arne — Wed, 22 Mar 2006 22:32:36 -0000

hi there,

is there any chance to use the plugin without harming the function allowed_tags() (used in comments.php to show what html tags are allowed)? whenever i active the textile plugin, it strips away allowed_tags' output.

Re: Textile Plugin 2.6 released

Jeremy — Mon, 20 Feb 2006 14:37:17 -0000

Great plugin, I love it!!!

I'm trying to push it a little further, to use it in titles and meta fields, and here's where I'm running into a problem:

Is there a way to keep Textile from adding p tags when the content is only one line long? Then I can hard-code a field to be a header, for example, without getting a nested p tag...

Any help you could offer would be appreciated.

Thanks!
-Jeremy