Hi everybody,
After searching the archives for 2 hours, i could find nobody with my problem.
I Downloaded the latest version CKEditor today, all working good.
I only have a problem using the config['EditorAreaCSS']
The styles in my custom CSS file are only applied after rebuilding the viewport,
ie.: toggeling between source mode and wysiwyg mode applies the stylesheet.
going to fullscreen mode applies it, when going back to windowed mode, it's still applied.
I think the custom CSS file isn't finished loading when the textarea's are swapped with the editor.
btw. all works fine on Operah 10.00
problem is on: firefox, swiftfox and IE (ofcourse)
server: Ubuntu Apache
Please help!!!!!
the code in index.php:
<?php
global $base_url;
?>
<script type="text/javascript" src="<?php echo($base_url)?>/plugins/ckeditor/ckeditor.js"></script>
<script type="text/javascript">
</script>
<?php
function wysiwyg_input($inputname,$preload,$width,$height)
{
echo("<textarea id=\"$inputname\" name=\"$inputname\" class=\"ckeditor\" rows=$height cols=$width>");
echo(stripslashes($preload));
echo("</textarea>");
}
?>
Re: EditorAreaCSS not finished loading when editor is created.
<script> CKEDITOR.tools.setTimeout( function() { CKEDITOR.replace('<?php echo($inputname);?>'); },5000); </script>this would give the script 5 seconds to download the css file, doesn't work.
Still need to go into fullscreen, and then back to normal mode to apply the stylesheet.
Re: EditorAreaCSS not finished loading when editor is created.
EditorAreaCss has now changed to ContentsCss.
Hope that still helps.
RT
Re: EditorAreaCSS not finished loading when editor is created.
For me, the problem is more likely to occur when the .css are not in the browser cache. Can you load the .css in the container page to get them into the local cache before you do the .replace?
Your timeout won't help as the download of the .css does not occur until after you .replace. As a kludge, how about putting the editor inside a div style="display:none", do the replace and then 5 seconds after the .replace do a display:block the div? Terrible, terrible kludge, but it would get you up and running until a real solution is found.