Yep, the problem was -I think- due to the different engine to parse the Textile syntax. In my plugin I used also the one from Textpattern and all was right.
If you've reverted to it, we could kill my version even from the wiki as soon as the new release of Vanilla ships. ;)
I've made one small modification to the txp-textile-code for use with Bergamot's Quotation extension: See this thread for more info.
The only other thing I've noticed is that the preview (SirNot's extension) sometimes looks screwy for special characters but when posted it is fine. Not looked at it in detail so any tips welcome. EDIT: in the meantime resolved.
EDIT: mini update to v 0.55. Separated code for easier updating of textile.
Sorry, man, got yr email and it's still sitting there with the "Reply to this, yo!" flag on it. It's been sorta hectic around here for me the last few weeks. I'm more than happy to just pass the deal off to you if you'd like it, I haven't been doing much work with Vanilla for a while now. I'll get back to you on the Ekwipment question later tonight. ;)
No matter nifkin, I'm not sour, just thought some of these guys here would like to give it a whirl :-) I was more worried about pigging-backing on your good work without you getting any credit. Ekwipment: thanks, still interested in that too :-)
folletto: any feedback is welcome. If all's okay it can be added to the add-ons.
Just one thing confused me: on 0.9 there was a user option to choose the default, now I think it uses the last choice. It's an "issue" due to Va1 I suppose. :)
This version now uses the most recent version of Textile 2.0.0 and adds some new features. For details of what is new in Textile 2.0.0. see the announcement on thresholdstate.com. Textile is now officially maintained by Alex Shiels. The add-on version number has been adjusted to match the Textile version.
Main differences:
Uses the new TextileRestricted function for handling untrusted user input which obviates the need of the previous stringcleaner function. This has a reduced feature set in comparison to the normal textile but is specially devised for safer user input. This means that all HTML is escaped and inline id, class and span attributes that are added with textile are stripped.
Textile Settings can be set through the admin settings area
Textile lite on/off
Inline images on/off
rel=nofollow (or alternative)
The standard settings are the most strict settings. They are safest but also most restrictive. Admin users can relax the settings somewhat.
Addition of Textile Help pop-up It appears in brackets next to the radio button and uses central Textile Help resource at threshholdstate.com. The add-on should pull the correct language version based upon the language string of the Vanilla installation. If your language does not exist, or you prefer otherwise edit the link in default.php.
Updated for vanilla 1.03 vulnerability correction
Note for updaters that the above could possibly result in some differences in behaviour since the previous version.
Yes, it has that IN_VANILLA else exit check at the beginning of the plugin that is only understood from v1.03. You should upgrade. If that's a problem you can remove the 4 lines above require('classTextile.php'); in default.php at your own risk.