Try double clicking and see if anything happens, also, you may want to enable the editing fields in the weblog (Admin > Weblog Management > Publish Page Customization and make sure that Display Formatting Buttons is checked). A single click is supposed to use those buttons, so if you’ve disabled it, you probably can’t single click on the field.
Let me know if that does it.
Actually that’s the problem. With v1.1.9 a single click enables the EE Formatting fields. Of course, if you have turned it off under the weblog management, it will not find it (hence it will give a js error of setNameField not found). The extension that i created isn’t smart enough…I mean i haven’t made it smart enough…to figure out if the formatting fields have been disabled or not. Sorry about the confusion…
Jit
can you post (or im me) the settings that you have for the extension? I would say that now that is the problem.
I realize that you have posted them above, but can you give them to me as you have it? Thanks
[Update]: Silly question, but you are pointing to the correct fckeditor location in the settings right? IE: URL of the FCKEditor Script: http://[your site URL]/FCKeditor/fckeditor.js
I’ve installed this extension and the FCKeditor scripts but when I goto the publish page, nothing happens.I’ve view the page source and the FCKeditor javascript and references are all there, but neither clicking or double clicking on any of the text areas does anything. I’ve triple-checked the extensiosn settings and everything seems to me in order. Is there supposed to be a link or something that opens the editor? Does this extension work with the latest version of EE?
This is what I have in my settings for the extension:
var oFCKeditor = new FCKeditor(textAreaName); //Configuration goes here oFCKeditor.BasePath = ‘http://www.mysite.com/system/fckeditor/’; oFCKeditor.ReplaceTextarea() ;
I looked at the documentation for FCK, but nothing jumps out at me. From what I can tell, there is no configuration needed for FCK, and all the sample scripts work as is.
Please let me know what I’m doing wrong, I really want to get one of these editors to work.
Sean
The naming convention (caps for FCK) with the name FCKeditor can cause problems on unix servers if the capitols are not taken into account in your paths. That tripped me up on one site myself initially.
I notice that in the path to the directory you use fckeditor but I think that it is usually capitalised (FCKeditor) by default. You may want to check that.
I’ve been having the same issue as everyone else, but I’ve made sure that everything is installed properly and my _sample folder worked fine?
URL of FCKEditor Script
http://www.re-volvemedia.com/FCKeditor/fckeditor.js
FCKEditor Configuration
var oFCKeditor = new FCKeditor(textAreaName);
//Configuration goes here
oFCKeditor.BasePath = 'http://www.re-volvemedia.com/FCKeditor/';
oFCKeditor.ReplaceTextarea();
When I go to the publish page nothing happens?
When I view the source code it looks like the JavaScript files are commented out? But I can not figure out which files to edit.
Seth, here’s my settings that I use:
URL of FCKEditor Script
http://www.websitename.com/FCKeditor/fckeditor.js
FCKEditor Configuration
var oFCKeditor = new FCKeditor(textAreaName);
oFCKeditor.BasePath = '/FCKeditor/' ;
oFCKeditor.ReplaceTextarea() ;
It’s possible Seth that the basepath needs to be a relative url - looks like you have given an absolute url for it.
I still had no luck and I tried these three:
var oFCKeditor = new FCKeditor(textAreaName);
oFCKeditor.BasePath = '/FCKeditor/' ;
oFCKeditor.ReplaceTextarea() ;
var oFCKeditor = new FCKeditor(textAreaName);
oFCKeditor.BasePath = '../FCKeditor/' ;
oFCKeditor.ReplaceTextarea() ;
var oFCKeditor = new FCKeditor(textAreaName);
oFCKeditor.BasePath = '../../FCKeditor/' ;
oFCKeditor.ReplaceTextarea() ;
I uploaded the FCKEditor files outside of the System folder? Should it be contained inside?
Edit:
Well I moved my FCKeditor folder inside my system folder and changed the paths to represent and still no luck?
var oFCKeditor = new FCKeditor(textAreaName);
oFCKeditor.BasePath = '/system/FCKeditor/' ;
oFCKeditor.ReplaceTextarea() ;
I am really confused.
Oops, sorry to make it sound confusing.
It should not matter where you put the FCKeditor files.
I guess what you should do now is to turn on javascript error messages (or check out the javascript error messages) on your web browser. If the files are not found, then the error should point to that. We could probably figure out what the problem is from the javascript message…
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.