The solution here was to move any end-user styles to RadEditor.css and then import RadEditor.css into skin.css url('path/RadEditor.css')). css and RadEditor.css) and also then list them in ToolsDefault.xml i.e. It then became apparent that you need to define your 'end-user' styles twice (i.e. Things started to work then and the remaining steps in Lance's inital post were pretty much 'bang-on'. Here's my experience and contribution to the debate.for what it's worth.:) Īt first I couldn't get anything working as regards styles in the Appl圜SS dropdown, then I went to Host>HTML Editor Manager and selected TelerikEditorProvider instead of DotNetNuke.RadEditorProvider.
Heading 6 Bold" value="" />
Heading 4 Book" value="" /> 
Heading 6& lt /H6& gt " value="& lt H6& gt "> Heading 6 Bold& lt /h6bold>" value="& lt span class='h6bold'>"> Heading 5& lt /H5& gt " value="& lt H5& gt "> Heading 4 Book& lt /h4book>" value="& lt span class='h4book'>"> Heading 4& lt /H4& gt " value="& lt H4& gt "> Heading 3& lt /H3& gt " value="& lt H3& gt "> Heading 2& lt /H2& gt " value="& lt H2& gt "> Heading 1& lt /H1& gt " value="& lt H1& gt "> Text Paragraph& lt /P& gt " value="& lt P& gt "> There are several threads on this topic and I've spent the day melding them all into a solution for DNN6.02 so that I can show accurate styles for the admins to select from that match the skin.cssUsing the HOST > HTML MANAGER, Toolbar Config Tab, the cleanest editor toolbar we are using now - including references to the styles "h6bold" and "h4book" named in the Skin.css that display in the editor properly comes from this:
0 kommentar(er)
