CMS Made Simple Forums

Hi! I'd like to suggest a checkbox button where would be possible to disable MicroTinyMCE on the fly.

It's because it automatically adds a 'p' tag even when I delete it from the code view mode.

Thank you!


Walter

TinyMCE has some more advanced features like an on/off checkbox. I believe the module's developer is working on a release for 2.0

In the meantime, you can disable it under the Options tab while editing a page, or use the "Source Code" view under Tools to edit those tags out.

But, keep in mind that a content page's default block cannot be empty when trying to save your changes.

JohnnyB wrote:TinyMCE has some more advanced features like an on/off checkbox. I believe the module's developer is working on a release for 2.0

In the meantime, you can disable it under the Options tab while editing a page, or use the "Source Code" view under Tools to edit those tags out.

But, keep in mind that a content page's default block cannot be empty when trying to save your changes.

Hi Johnny! Yes, I used to use TinyMCE and this resource before.

I'm doing exactly what you suggested, disabling under options tab. I tried to delete the 'p' tag in "Source code" view, but it reappears automatically. Other tags can be deleted normally, but this not, at least didn't work for me.

Thank you!

You can create a custom tinymce_config.js file by copying the one that comes with MicroTiny. There are tinymce 'rules' that can disable automatically forcing a new paragraph. Check out the TinyMCE version 4 documents for the tiny.init()

You create a custom tinymce_config.js file by using the same "module_custom/MicroTiny/templates" method described here for module templates in the Admin: http://docs.cmsmadesimple.org/customizi ... -templates

The wysiwyg editor can be disabled
a: for individual content blocks by specifying it in the template
b: for the entire content page
c: for the user

So there's really no need to have any more mechanisms.

If you are going to be putting your own design elements into a content area then you really aren't expecting a non-designer/developer user to be editing that content. or at least you shouldn't be. so you can disable the wysiwyg for that content page and not allow your editors to edit it.

If you are allowing content editors to edit the content of a page then the <p> tags are a good idea.

Unless they are adding a module tag like {News} where MT will wrap it in a <p> no matter what you do...

and a call to a module like {News} is a design element. that's part of your design. A content editor should not be expected to know that stuff or deal with it. and therefore prolly shouldn't be editing that page.