The OTHER way to do this is to create a container on the page that allows you to reference your css into it much like you would have done via an anchor. Of course, to do this, you really need to have your css exist in RD as a content class.
I have a generic container content class set up in my main project so that I can connect smaller content class chunks of css to make a modular css file. This allows me to then modify the css ever so slightly on the fly depending on the actually needed inside a project. The main pain point in doing this is attaching all of the background images that are needed in each project. Anyway, if your CSS is done in this fashion, you can attached it like you normally would via an anchor and then surround that with "not in reddot" tags and then use a style tag with a container to inject the css directly into the page itself while in smartedit. On May 13, 5:04 am, bobbykjack <[email protected]> wrote: > That's another good tip, Joshua, but I believe that could cause CSS > inconsistencies unless you're VERY careful! > > Cheers, > > - Bobby > > On May 12, 6:03 pm, Joshua <[email protected]> wrote: > > > > > > > We typically wrap the DOCTYPE decl in <!IoRangeNoRedDotMode> within > > the template. Any sort of doctype indicates to Firefox "we know what > > we're doing, so expect this to be valid." The absence of a doctype > > indicates to Firefox, "we don't really know what we're doing... so be > > as generous as possible with our non-compliant HTML." That way you can > > get standards-compliant (X)HTML published, but Firefox will be more > > forgiving of SmartEdit quirks. > > > On May 12, 12:44 pm, bobbykjack <[email protected]> wrote: > > > > Hi all, > > > > I'm trying to deal with the (seemingly commonly known) RedDot bug > > > relating to the Mime-Type of a CSS file. Since Firefox rejects > > > stylesheets with the wrong mime-type, and RedDot CMS serves all > > > template-based content as text/html, there's a page-preview/smart edit > > > problem when the two combine. > > > > I've noticed this previous thread on the subject: > > > >http://groups.google.com/group/reddot-cms-users/browse_thread/thread/... > > > > but adding "&Script=1" doesn't solve the problem for me. I've also > > > seen what happens when a media element is used instead (as suggested > > > in that thread), and it seemed like a lot of hard work when styles > > > change fairly frequently (as they do in our case). > > > > Has anyone come up with a proper solution for this? > > > > Cheers, > > > > - Bobby > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "RedDot CMS Users" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group > > > athttp://groups.google.com/group/reddot-cms-users?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "RedDot CMS Users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/reddot-cms-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/reddot-cms-users?hl=en. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
