Would move your javascript into the approprate place
next.
In your theme, make sure that you have a template.php
file which contains the following, then remove the script tag from your theme.
function _phptemplate_variables($hook, $vars)
{
drupal_add_js(path_to_theme().'/global.js','theme');
}
ok - just tested it - it's not the
*{} css block. it must be something else in the theme, something i'm
missing perhaps.
sander-martijn wrote:
New
info: when i change my site to one of the default themes it works, so it's
something in my theme. I'm a first time drupal theme developer so i
suppose that's not terribly surprising.
Relevant notes about my
theme:
I am including the following in my theme:
<?php print
$styles ?>
<?php print $scripts ?>
<script
type="text/javascript" src="<?php print base_path() . path_to_theme()
?>/global.js"></script>
so that should be including
any required drupal css and js
(p.s. - i'm sure there's a way to get my
custom javascript into the scripts variable but i couldn't figure it out
from the documentation and the themes that i downloaded that used javascript
were all doing it this way. i'd love to do it the proper way
though)
my javascript isn't doing anything that should break these
editors. There's no styling in the css for textareas. However
there is this global css declaration - I've gotten into the habit of always
setting this and then overriding when necessary because I've found it makes
my life easier. It's the only thing i can think of that might cause
it, other than a block of php code i need to include that i'm
not:
*{
margin:0px;
padding:0px;
font-family: arial, helvetica, sans-serif;
font-size:
12px;
line-height:19px;
color:#46403a;
}
specifically the margin and/or padding being set
to 0 on textareas... I wouldn't think that would mess it up, but it's all
i've come up with so far
.s
Metzler, David wrote:
I haven't done this with 5.2 but I'd been planning on
upgrading. I will do this and get back to you. I'm a long time
user of TinyMCE, so I ought to be able to figure this out quickly.
Dave
Ok, having a simalar but
not quite the same issue with fckeditor. with fckeditor i can edit
the admin options. I realized with both that i have to enable them
in roles so i did that. I also tried uploading them into /modules
instead of sits/all/modules/ but no change, still getting plain text in
edit fields. Any suggestions? Drupal will be pretty much
useless for me if I can't get wysiwyg working (even though i hate it
myself, the client can't handle it otherwise).
sander-martijn
wrote:
and now for my own support question. As my client is not html savvy,
one of my early requirements is to get a wysiwyg editor working. I
chose tinyMCE as the first trial because I'm thinking IMCE will be a
good add-on (although on second look it now also supports FCK so if I
can't get an answer here i may just try that). I downloaded the tinyMCE
module official release 5.x-1.9, downloaded tinyMCE version 2.1.1.1 and
put it in the directory as specified and uploaded it. I enabled the
module in admin but it didn't show up. Figured I had to configure it so
went to the tinyMCE configuration page but that page is blank. I'm on
drupal 5.2 and I noticed the note (or copy the TinyMCE files into the
module's includes folder for the 5.2 users) but there is no includes
folder in the version i downloaded.
Does anyone know whether I should create the includes folder or have to
download the dev version (always should be a last option in a production
site of course), if i need a different version of tinyMCE or some other
issue I might be having?
.s