Will dance for Textile

channing

Are there any logs produced by vanilla I could look at to see what the problem might be?

Minisweeper

No, actually. But that's not such a bad idea. Though i'm sure it'd take a *lot* of work on the codebase but log production might be a nifty feature.
Vanilla does, however, print most errors to the screen (in a human format) so chances are really that the log would just contain what it would otherwise echo out. The only time it doesnt print errors is on the actual php function errors because theyre all silenced with the aim that the vanilla error checking thing will pick up the problem and tell us it more usefully. If you coud find the function thats being used when people click to save a comment and remove the @ from the front it'l echo any problems it's having if there are any. Which function it is i'm not sure, sorry.

channing

Thanks minesweeper, I'll have a dig around. Channing

folletto

I've developed indipendently a TextileCode extension... I've seen this one just too late. but... I've used the original textile() function and adapted it... seems that this one doesn't have any encoding problem (at least for all my chars). Please, try it out ;)

nifkin

folletto: you have a URL for that?

folletto

Whoops ^^' Sorry, I forgot to mention that I linked it in the wiki: http://lussumo.com/docs/doku.php?id=vanilla:extensions It's here: http://www.digitalhymn.com/projects/vanilla

jakob_r

I've updated nifkin's textileformatter extension for forthcoming vanilla 1.0 and have it working fine with latest svn 294 on a local install. To be fair to nifkin, I've passed it back to him first to look over/adjust as he sees fit.

folletto

Just a question: are all the problems of the original extension still there (i.e. UTF-8, errors)?

jakob_r

In my test situation it does not throw up errors and works fine with German characters, quotes, double-dashes etc., but I do not know what problems the previous version threw up.

I exchanged textile 2.08 wholesale for the current textile implementation from textpattern, primarily because I am more familiar with it and because it has gone through some rigorous testing in the txp community. It seems to work fine for me and I was able to remove the error_reporting(0) from the plug-in, whilst keeping nifkin's code to trip up javascript, onMouse... etc. and embed being executed.

I've noticed that some small CSS modifications in vanilla or extensions may be necessary for the message windows and preview field as a result (one already mentioned on the dev forum), but that would apply in any case.

folletto

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.

jakob_r

Well I've had no reply from nifkin for 12 days, so try it out for yourselves and see if there are any problems: download textile extension version 0.55 for Vanilla 1.0.

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.

nifkin

Well I've had no reply from nifkin for 12 days

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.

folletto

Ok, I'm not able to test that out yet, but I surely try it when Vanilla 1.0 will be out officially, since I will put that on my website.

jakob_r

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.

folletto

On Vanilla 1, just upgraded, works perfectly.

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.

ionfish

Just got this running here, no problems so far. Nice work, much appreciated.

folletto

I've been contacted by a nice person that noticed me about Textile 2.0.0, just released.

It's here:
http://textile.thresholdstate.com

jakob_r

Textile 2.0 Update

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.

Get it here!

Thomas Heath

I get blank-screen-no-vanilla when I enable Textile - any thoughts why? I'm not running 1.03 yet - is that prerequisite?

Minisweeper

It may well be, and even if it's not I'd suggest you upgrade anyway.