FCKEditor does run with XAMPP
- see the BTW comment.
It will give you much more useful error messages than IE's "object expected" (which can mean many things).
A *.js file is more than likely referred in your script's php or html pages by a relative path instead of an actual path which XAMPP is having trouble with.
This is a common problem in some scripts that rely on relative paths and can raise this issue in many ways and is often hard to track down.
- Code: Select all
where xampp.js would be the file name of your particular script's something.js file.
If it doesn't have a path in front like the above, then the something.js file should be in the same folder as the html or php file calling it.
- Code: Select all
or something similar.
This may cause your issue when running on XAMPP but may not cause an issue on a Linux based commercial server or when you run the script from the script's directory, as in your case.
It all depends where you have located your editor script within the XAMPP htdocs tree.
The errors you are having are all script related to path locations within your editor directory and XAMPP's htdocs structure.
Do a Google for these specific key words and you may find a more suitable explanation for your particular situation.
1. FCKeditor object expected
2. 'FCKLang' is undefined
3. 'FCKLang' is undefined
In the results of the above searches you may find that your issues are not peculiar to your situation and you will more than likely get a better understanding of them.
From reading some of the replies myself from the first keywords above I notice that this was/is a bug in FCKeditor in how it handles paths.
As I said before, it is not a specific XAMPP problem only a path that XAMPP is not able to translate into a location.
I just downloaded the FCKeditor 2.4.3.zip
and extracted it to my XAMPP's htdocs directory:
I then went to:
I had the fckeditor with a list of samples I could select with all of them working when I selected each individual sample, just as they should, with absolutely no errors
I did not change any configuration settings at all.
So for me this FCKeditor worked 'right out of the box'
There is nothing wrong with the way XAMPP handles fckeditor.
You have a problem with the way you installed it.
Try what I did above and see if you get the same result.
http://wiki.fckeditor.net/Developer.s_G ... stallation
Take a look at the new DeskTopXampp
launch control posted by ridgewood
http://community.apachefriends.org/f/viewtopi ... 967#103967
launch control for XAMPP
is available here:
I highly recommend DTX.