By mcsolas on

The tinymce module works great.
Im very happy to see tiny integrated into drupal, its my RTE of choice.

After installing and getting the instances to show up properly, I ran into a few issues.

1.
I am using the zen theme, and set a black background.
The background inside tiny is doing the exact same thing.
How can I prevent this?

2.
Im already wondering about a how I can make tiny render in 1 line, instead of the following code:

theme_advanced_buttons1 : "bold,italic,underline,bullist,numlist,link",
theme_advanced_buttons2 : "image,forecolor,sup,code,hr,removeformat,charmap,flash",

\/ \/ to this \/ \/

theme_advanced_buttons1 : "bold,italic,underline,bullist,numlist,link,image,forecolor,sup,code,hr,removeformat,charmap,flash",
theme_advanced_buttons2 : "",

Im not sure what dictates that it writes the tiny init script like this.
I also just saw tiny instantiate itself differently when I went to edit the signature in the user pages... with the menu at the bottom even though the only profile I created specifies it to be at the top ( and I would have expected the 2 line install to popup )
mode : "exact", theme : "simple",

The signature instance kind of threw me off .. Im not sure what dictates that behavior.

⋅ Categories: Drupal 5.x

Comments

PixelClever’s picture

PixelClever commented

I ran into that problem when I built my last site. The solution is to give the body in your tpl a css class example: body class="my_custom_body" and style it as you want the main page to appear . Then you style the main body tag with a white background. I don't know if this is the correct approach, but it works and seems to be valid code.

mcsolas’s picture

mcsolas commented

However, I looked at the body and it already has quite a lot of 'class':
<body class="front logged-in sidebar-left">

What about an ID tag?

Going to poke around on the tinymce site. I remember finding a post on this some time ago.

----------------------------
www.pacificallsurf.com

mcsolas’s picture

mcsolas commented

Im taking a closer look at the inherited into the iframes body tag using firebug.

* Note strings "style.css (line 87)" arent in the css, that was text that tagged along from firebugs display.
They should be useful to include in this case:

Here is some of the condensed css to work on:

body {style.css (line 87)
background:#000000 none repeat scroll 0%;
}
body {style.css (line 65)
min-width:800px;
}
body {editor_content.css (line 6)
background-color:#FFFFFF;
}

The min-width:800px; one is creating a horizontal scroll bar at the bottom of the text area ( browser Firefox 2 ).

How can I properly cancel these declarations?
Or re-structure the style.css document to avoid inheritance?

----------------------------
www.pacificallsurf.com

PixelClever’s picture

PixelClever commented

Some themes come with sub-theme css or alternate css for different browsers. If these styles are affecting your page and you don't find them in the main css try looking in any sub-folders included in the theme. It appears that min-width is being declared somewhere, usually all you have to do is find it, copy the syntax, then give it the attributes that you want it to have on your main css page which will thereby override it. Or, if it so happens that you find that this css originates from a subfolder style sheet, you can most likely delete the style directly. If worst comes to worse you can do a site-wide search with dreamweaver to look for the min-width.