Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
option to save comments in Textile format.
Hi.
That is: to have a preferences option for saving comments in Textile format.
Similar to article body and article excerpt, that are saved in Textile format, it would be nice to have the visitors comments saved in Textile format.
Sometimes, I find myself editing comments (particularly, for correcting typos and links in a site where comments are used for product reviews) and it will be easier to have them save in Textile mark-up.
Also, not totally related, but… weren’t there an option to use Textile in link (Content->Link) description? I swear I have seen it in previous TxP versions…
Offline
Re: option to save comments in Textile format.
Also, not totally related, but… weren’t there an option to use Textile in link (Content->Link) description?
Yep, I’ve seen it too in previous versions. So, yes there have been.
That is: to have a preferences option for saving comments in Textile format.
Currently there is a option to choose from extended or lite textile formating for comments. But it’s formatted while saving so, you have to edit the xhtml, if you wish edit anything.
easier to have them save in Textile mark-up.
Actually, current way is a little faster – it’s the positive-point in it.
Cheers!
Offline
Re: option to save comments in Textile format.
maniqui wrote:
weren’t there an option to use Textile in link (Content->Link) description?
It was removed in Txp 4.0.5 as this feature wasn’t consistently applicable across all use cases (website, feeds). We need some more rethinking about Textile beyond its current use for articles. This also applies to comments or image descriptions.
Last edited by wet (2007-11-28 06:50:26)
Offline
Re: option to save comments in Textile format.
What about addding in mysql extra table with textiled version of content?
Providing help in hacking ATM! Come to courses and don’t forget to bring us notebook and hammer! What for notebook? What a kind of hacker you are without notebok?
Offline
Re: option to save comments in Textile format.
What about addding in mysql extra table with textiled version of content?
You mean comments, right? Articles are already saved as they are at that point. But what is your point in that matter? It doesn’t help anything you know, it only uses space, by Textiling could be done on-fly etc.
Cheers!
Offline
Re: option to save comments in Textile format.
on-the-fly Textiling is too slow.
I think that Julián is asking for the original comment with textile markup to be saved as well, which makes it a lot easier to edit comments if needed, because currently you have to edit the end result (HTML) instead of what the user entered (textile). I personally think that this would not be a waste of space.
Offline
Re: option to save comments in Textile format.
Yes, that is what I asked: to save both versions, like it’s done with articles. The Textile version for easier edition, and the HTML version to avoid the Textile-on-the-fly.
Offline
Re: option to save comments in Textile format.
Yep, but some of use have a quite little webspaces with a even worst mysqls. So, it could be a option, not have-to-do thing. But what about lite untextile, that turn xhtml to textile when editing comment in backend? Yeah, I know it has it own faults and misspoints, but it could be also done.
on-the-fly Textiling is too slow.
I know, as I said in my earlier post: “Actually, current way is a little faster – it’s the positive-point in it.” Because, I thought that Julian meant that comments are only saved in Textile version.
Cheers!
Offline
Re: option to save comments in Textile format.
We already do the exact same thing for articles, so I personally think it would be a good idea to do the same for comments. Yes, it uses a bit more space, but if that little bit extra is causing you problems, then you’d have to upgrade your webhosting account anyway to be able to have more articles on such a website ;)
It’s unlikely to happen in 4.0.x, but definitely something to consider for 4.1.x.
Offline