Sebastian Leupold wrote
| ErikVB wrote
the limit is quite probable. If you need to filter a lot of styles, it might be easier to just create your own static css for the editor
|
Erik is not quite correct, you need to create a custom FCKstyles.XML; there are a couple of howTos and explanations avaliable in the web. You can specify the file in advanced editor settings per portal, module or instance.
thats basically what i said but more elaborated :) AFAIK you must change the fck editor styles setting from dynamic to static.
What i typically do is make these changes in web.config:
<add
name="FckHtmlEditorProvider"
type="DotNetNuke.HtmlEditor.FckHtmlEditorProvider.FckHtmlEditorProvider, DotNetNuke.FckHtmlEditorProvider"
providerPath="~/Providers/HtmlEditorProviders/Fck/"
CustomConfigurationPath="~/portals/_default/fck/FCKConfig.js"
EnhancedSecurityDefault="false"
SecureConfigurationPath="~/portals/_default/fck/FCKConfigSecure.js"
ImageGalleryPath="~/Providers/HtmlEditorProviders/Fck/fckimagegallery.aspx"
ImageUploadPath="~/Providers/HtmlEditorProviders/Fck/fckimagegallery.aspx"
ImageAllowedFileTypes="gif,png,bmp,jpg"
FlashGalleryPath="~/Providers/HtmlEditorProviders/Fck/fckimagegallery.aspx"
FlashUploadPath="~/Providers/HtmlEditorProviders/Fck/fckimagegallery.aspx"
FlashAllowedFileTypes="fla,swf"
LinksGalleryPath="~/Providers/HtmlEditorProviders/Fck/fcklinkgallery.aspx"
DynamicStylesGeneratorPath="~/Providers/HtmlEditorProviders/Fck/FCKStyles.aspx"
DynamicStylesCaseSensitive="true"
DynamicStylesGeneratorFilter="controlpanel|filemanager|mainmenu|wizard"
StaticStylesFile="~/Portals/_default/fck/fckstyles.xml"
StylesDefaultMode="static"
DynamicCSSGeneratorPath="~/Providers/HtmlEditorProviders/Fck/FCKCSS.aspx"
StaticCSSFile="~/Portals/_default/fck/fck_editorarea.css"
CSSDefaultMode="static"
spellCheck="ieSpell"
AvailableToolbarSkins="Office2003,Silver"
DefaultToolbarSkin="Office2003"
AvailableToolBarSets="DNNDefault,Default,NoGallery,Basic"
DefaultToolbarSet="Basic"
DefaultImageGallerySkin="Default"
DefaultFlashGallerySkin="Default"
DefaultLinksGallerySkin="Default"
FCKDebugMode="false"
UseFCKSource="false"
OptionsOpenMode="ShowModalDialog"
CustomOptionsDialog="Admin"
ShowModuleType="true"
FixOldDNNPostback="false" />
The highlighted lines are the ones that are changed (this is from memory, i might have missed one or more). This will put the complete fck config in the portals/_default folder, so it can be easily reached by the host user, and not modified by the admins. the fck_editorarea.css file defines the css that is used for the editor area, this should match your skin as much as possible. fckstyles.xml defines what styles are available in the styles dropdown. What dropdowns are available is defined in fckconfig.js. What i typically do on most sites where admins are only allowed to edit basic html is to set the basic toolbar to be used as default, and modify the definition of this basic toolbar to the needs of the site.