TinyMCE kills Ditto and all known Snippets

Hi,

More advisory for Newbies than a question.

A while back I had a problem with Ditto. Some combinations of parameters worked some didn’t. Eventually discovered that I had been editing Ditto in a page ’resource content’ with TinyMCE on which resulted in odd HTML Spans appearing (shown by turning TinyMCE off) which messed up the Ditto Call (and probably other snippet calls). So in Security - Manage Users - Users - I set ’Editor to use’ to none. So no more TinyMCE - anywhere. Great... but

When it comes to the Editor Users they will prefer to use wysiwyg Editors but this will also screw up Ditto calls (and other Snippet calls) in pages.

The real problem is that I wasn’t using the Document Resource Content for just that - Content. So, the Snippet calls should really have been in the Template or a Chunk called from the Template (and/or perhaps a Chunk called from the Content? - I think that would be appropriate).

But I like not using TinyMCE but need it for Editors who don’t want to even see HTML far less use it.

So I’m trying to come up with a process. E.g. All calls to functions/snippets from Templates or Chunks. All Content Pages using TinyMCE by default but all Templates/Chunks use No Editor. And for this to be setup automatically from some settings rather than manually on each page/element.

I did suggest to one of the Developers that TinyMCE is so dangerous that it should be Off by default (maybe just for the non-content ’techie bits’. He stated that he never uses RTE’s of any kind (so all pages altered in HTML) but this is no good for everyday users.

Any Views?

Update
I have created an Editor user. They cannot see Templates but can see Chunks. This would suggest that if they open a Chunk which contains a Snippet call with TinyMCE on as default then that Ditto/Snippet will be instantly corrupted. Can’t be good.

Well, many of the more complex snippets like Ditto will use an external config file, so you would only need one parameter in the snippet call, the filename of the config file. Or you can put all snippet calls with parameters in TVs and assign the TV to a document group that the editor users don’t have access to, so they won’t even see the TV.

Susan,

Snippets have Config Files! Crikey. Had a look through documentation/forums and even when I know what to look for there isn’t much mention of Config files. Is there something that explains this approach?

I wonder if perhaps now is a complex time to be a Newbie. Revolution will be taking up much development/testing effort and I believe the old Wiki/Docs are being transfered into the new system (which appears not to have got very far). I’m never very sure where the best place to find documentation is. I do struggle a bit with where is the best place to do certain things - I think MODx has a lot of flexibility in this regard (which is good) but can get a bit confusing.

Odd thing is that TinyMCE Snippet Destruction must be something that happens all the time... yet I haven’t found any mention of the issue.

I’ll keep those suggestions in mind but perhaps keeping the Snippet calls in the Template is equally good?

Parthian