TinyMCE Removing

Hi all,

It seems like this is a fairly common issue, based on posts here and in other communities. I’ve read through some of the solutions and comments already in the MODx forums, but I haven’t found anything that directly addresses the <DIV> tag issue as does this article: http://www.mkbergman.com/?page_id=383 (scroll down to "Changing Code Processing").

I am trying to nest a <DIV> tag that serves as a "clearer" (i.e. clear: both;). I actually edit the raw code, then save the changes (my environment is set to use TinyMCE as a default). The first time I save the change, it works as expected in the browser. The next time I edit the page with the clearing <DIV>, it’s gone. If I resave without adding the <DIV> back in or making any other changes, the page no longer works as expected in the browser (which makes sense because the <DIV> is gone).

What is the best way to prevent TinyMCE from removing this <DIV> that is added into the raw code? According to the above article, I need to edit a TinyMCE configuration file.

Is there a better fix for the MODx environment?

Thanks,

Chris
MODx v 0.9.6.2
TinyMCE v 3.1.0.1a

I work with TinyMCE through NewsEditor/Manager and in that snippet there is a variable: $allowed_tags that let me set what is allowed. That is one way...

//But don’t write xhtml tags in capital letters.

Thanks. I guess I’ll look into snippet variables? I’m simply editing the content area of a basic article. I am calling the article via Ditto. Seems like there would be a way to universally "fix" this behavior in TinyMCE.

As for the capital tags, I always use lowercase. I just used uppercase in this post to highlight the tag...

Chris

Reading a little bit more into the article I referenced, I hunted down a possibility. There’s a file (xconfig.js) in the TinyMCE plugin directory that includes something similar to the valid_elements variable referenced in the article. The <div> tag does appear in that file in this context:



I’m not sure what this code means, since it doesn’t follow the same logic pattern as the code referenced in the article I pointed to.

Does anyone know if this is where I should make changes?

Chris

Some links that may lead you somewhere...

CSS:
http://modxcms.com/forums/index.php/topic,21255.msg131312.html#msg131312

Predefined Templates:
http://modxcms.com/forums/index.php/topic,30069.msg182569.html#msg182569
http://modxcms.com/forums/index.php/topic,31097.msg188847.html#msg188847

Use Plugins:
http://modxcms.com/forums/index.php/topic,32345.msg196786.html#msg196786

Config editing:
http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/force_br_newlines

In Evo 1.0.3:

Open the following file:

assets/plugins/tinymce/js/xconfig.js

Locate the div element within the string. Note that there may be a - prepended to it. The - flags the element for automatic removal if it is empty. By removing the - prefix, you will preserve the div element, even if it’s empty.

Save the file when finished, clear your browser cache, then refresh your browser.

For more info:
http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements

- Mike