Our code-base hasn't been upgraded in quite a bit, it seems. Now, when I drop in the new files and alter the fckconfig.js file in the appropriate manner, it does not work. (I am using a symbolic link to point back and forth between new and old versions.) Point to old code-base, the toolbar shows up; point it to the new code-base and it does not. So, I am thinking that the way to call the toolbar has changed too. Here is how we used to call it:
What think everyone? I have seen that the upgrade advice has not gone as far back as my version.
<script type="text/javascript" src="/FCKeditor/fckeditor.js"></script>
<script type="text/javascript">
function initFCK()
{
var oFCKeditor = new FCKeditor('content');
oFCKeditor.BasePath = "/FCKeditor/";
oFCKeditor.Height = 475;
oFCKeditor.ToolbarSet = 'CSU';
oFCKeditor.ContextMenu = ['Generic','Link','Anchor','Image','BulletedList','NumberedList','TableCell','Table'];
oFCKeditor.Config['BaseHref'] = "<TMPL_VAR NAME=CURRENT_ABSOLUTE_PATH>/";
oFCKeditor.Config['FullPage'] = true;
oFCKeditor.Config['ImageBrowser'] = false;
oFCKeditor.Config['LinkBrowser'] = false;
oFCKeditor.Config['FlashBrowser'] = false;
oFCKeditor.Config['LinkUpload'] = false;
oFCKeditor.Config['ImageUpload'] = false;
oFCKeditor.Config['FlashUpload'] = false;
oFCKeditor.ReplaceTextarea();
}
/*
**
** Enable FCKeditor only if the document being edited ends in html or htm
**
*/
var documentName = "<TMPL_VAR NAME=filename>";
var documentNameParts = documentName.split(".");
var documentSuffixIndex = documentNameParts.length - 1;
if (documentSuffixIndex > 0) {
var documentSuffix = documentNameParts[documentSuffixIndex];
if (documentSuffix.toLowerCase() == "html" || documentSuffix.toLowerCase() == "htm") {
window.onload = initFCK;
}
}
</script>What think everyone? I have seen that the upgrade advice has not gone as far back as my version.