, And thank for the tips to use untill the function will be add to ModX.
Quote from: OncleBen31 at May 10, 2006, 08:28 AM
BUT I WONDER if there is a way to use this document in the configuration of the manager : in manager / panel admin / sub-panet configuration / editor configuration / field CSS field path
I am curious how to do this. I’ve given TinyMCE as my content editor, updated my Path to CSS file to the direct css path, and then went into Manager to edit the content and nothing drops down from the styles menu...
I feel like I might be missing something. My client really wants all the specific styles to be within the content editor. It seems like this is the way to do it, but perhaps I’m missing a step?
Appreciate any help
It is possible. In fact, I just tried it out by populating the "Path to CSS file" field under "Interface & Editor Setting" in the System Configuration with a MODx-based CSS document and it worked fine. Main thing is to use the full path with the alias name of the document. Worked great for me. However, depending on how the CSS is formatted you may end up with unpredictable results...especially with FCKEditor. TinyMCE works better for this and even populates the Styles dropdown with the classes in the CSS. However, it does not populate it with highly complex classes or the ID’s of the CSS document. What I would do is create a separate CSS document that is written specifically for the RichText Editors. The benefit is that you can tweak the CSS so that the dropdowns are correct and so that the code is rendered correctly to mimic how the content might look when it’s published. It’s a bit of extra work...but the results are more than worth it.
