TinyMCE issues with css

Tobias Gladh

Vote:

Reading the new features of the upgraded TinyMCE and that it should be able to parse the EditMenuTitle and EditMenuName. Having a editor css set in the episerver.config the Styles section of the editor is very weird. It starts with a whole list of weird epi_ tags like epi_dc_title. It then doen't parse the EditMenuName on any of the tags that have it. Some of the tags are included in the styles dropdown, like h1, h2 and a specific eurostileRegular tag wich would indicate that EPiServer is reading the correct file.

But what is wrong? What are those epi_ tags coming from and why isn't the css parsed as it should be?

Using EPiServer CMS R2 with Commerce R2 SP2

#58971

May 14, 2012 17:06

Minesh Shah (Netcel)

Vote:

We just created our own editor.css and updated uiEditorCssPaths in EPiServer.config, after this our heading's were updated in tinyMCE. The default ones you mentioned above no longer appear

Our editor.css file looks like

/* EpiServer Editor css */

@import url(/css/default.css);

@import url(/css/responsive.css);

H2 { EditMenuName: Heading H2; }

H3 { EditMenuName: Heading H3; }

H4 { EditMenuName: Heading H4; }

H5 { EditMenuName: Heading H5; }

H6 { EditMenuName: Heading H6; }

P.small, .small { EditMenuName: Paragraph - small text; } P.big, .big { EditMenuName: Paragraph - big text; } P.pdf { EditMenuName: Paragraph with PDF link; } .stopFloat, P.stopFloat { EditMenuName: Start Paragraph in a new line. End floating. }

IMG.pullLeft { EditMenuName: Image - float left; } IMG.pullRight { EditMenuName: Image - float right; } IMG.frame { EditMenuName: Image - in border frame; } IMG.figure { EditMenuName: Image - resizable; }

UL.items { EditMenuName: Unordered list with bottom borders; } UL.next { EditMenuName: Unordered list with arrows; } OL.imgNumbers { EditMenuName: Ordered list with image numbers; } UL.pdf { EditMenuName: Unordered list with PDF icons; }

TABLE.zebra { EditMenuName: Zebra table}

#59008

Edited, May 15, 2012 17:30

Tobias Gladh

Vote:

Yes the css we were using had to much other stuff in it wich seemed to cause EPiServer problems when parsing.

#59029

May 16, 2012 15:35