On the template I put this at the very top, before the html start tag:
Code: Select all
{content block="custom" page_tab="main" assign="custom" label="Custom Content" wysiwyg="false"}
Code: Select all
{$custom}
Code: Select all
{content block="custom" page_tab="main" assign="custom" label="Custom Content" wysiwyg="false"}
Code: Select all
{$custom}
If this behavior is a feature I'd like it to be documented, if it's a bug, well, is there a bug-tracker?carasmo wrote:I think the editor works just as intended
http://www.tinymce.com/develop/bugtracker.phpКолючка wrote:If this behavior is a feature I'd like it to be documented, if it's a bug, well, is there a bug-tracker?
Have you visited the tinymce.com reference docs or searched for (or asked about) this on their forum? TinyMCE has many "documented" cleanup-related config. options that may (or may not) let you "cripple" the editor to your liking.Колючка wrote:...That's not my point. I just don't like undocumented, unpredictable, "undisablable" thing. ...
And why this "everybody" people are expect this? Look, I'm a newbie in html wysiwyg editing and I didn't expect it will "correct" my code without forewarning.Jos wrote:when everybody expects it to correct their code
If it was only in TinyMCE thing I'd surely visit their forum, but I saw it in MicroTiny, TinyMCE and FСКeditorХ wysiwyg editors, and I certainly thought that was cms's problem.fredp wrote:Have you visited the tinymce.com reference docs or searched for (or asked about) this on their forum?