Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNN6 RadEditor custom stylesheetDNN6 RadEditor custom stylesheet
Previous
 
Next
New Post
9/2/2011 11:48 AM
 
Igor Grigoryev


Joined: 10/23/2009
Posts: 2
Hi all,

I have a DNN6 instance with several portals installed. Each portal has its own skin and should also has its own RadEditor css file, BUT all portals have the same backend skin, placed in "_default" portal folder (say, "Portals/_default/Skins/AdminSkin").

In "Host - HTML Editor Manager" I can set the proper css file for RadEditor, but the path is relevant to skin folder, so DNN looks in "_default/Skins/AdminSkin" folder.

Can I configure RadEditor somehow separately for each portal (in this case I can write a path, for example, "../../../0/editor.css" for Portal0 only)?
Or can I use some token like [PortalRoot] to force DNN6 search the css file into current portal's folder and not into "_default" portal folder, where backend skin is placed?

Another solution is to copy backend skin into each portal's skin folder, but it'll be really weird to do this because of just one different editor.css file.


Any feedback or ideas will be appreciated.
 
New Post
9/30/2011 1:53 PM
 
10PoundGorilla-Golden

Joined: 8/8/2007
Posts: 9
Igor,

From what I can tell in setting up a custom CSS styles in the editor in DNN 6, it actually references the portals folder. So if you have several portals you should be able to have separate CSS files that would appear int he Apply CSS dropdown box.

All you have to do is create a CSS file and put it in the root folder of the portal. So for the default portal, portal 0, create a CSS file and call it editor.css. Then put that file in the portals/0/ folder. In the HTML editor configuration under host, make sure you have editor.css and NOT /editor.css.

For every other portal you would just do the same thing. Create a CSS file, drop it into that folder with the same name - portals/1/editor.css.

Hope that helps. From my testing that should work.

Dustin
www.10poundgorilla.com
 
New Post
10/20/2011 8:40 AM
 
Igor Grigoryev


Joined: 10/23/2009
Posts: 2
Seems like it works.
Thanks!

May be I was a bit confused by this DNN "hint":

- The css file to be used by the editor in wysiwyg mode. This file must reside either in the skin directory or in the portal directory. The path set here is relative to its parent (e.g. /editor.css is a file in the root of your skin)
 
New Post
3/16/2012 6:30 PM
 
Thomas

Joined: 10/29/2007
Posts: 201
I agree, that "hint" is totally wrong. It should be changed. I looked in the Language Editor to see if I could change it there for the Telerik HTML Editor Providers, but could not find it there.

You can include an editor skin in with your skin package, however. You would just set the CSS File field in the Editor Manager to be:
skins/mySkin/editor.css

Where "mySkin" would be the name of your skin package. I tried doing this using the regular css file from my skin package, but that usually has a number of qualifiers in it, like H1 defaults to something, but if it occurs within this or that class, then it looks like it does on your page. So a special css file just for the editor is usually needed.
 
New Post
3/20/2012 7:01 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212
please log the help text error into the public issue tracker at support.dotnetnuke.com. Thank you.
Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNN6 RadEditor custom stylesheetDNN6 RadEditor custom stylesheet


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out