I've just installed FckEditor for the first time, configured it and it seems to be running correct. I can upload images and create folders in browse. No problem there.
However when I choose a image it comes up broken in the editor. It seems to be a path problem. Ive including the editor in a parent directory, as followed:
/admin/editor.php
and images are uploaded to the following folder:
/admin/fckeditor/editor/filemanager/connectors/php/userfiles/
And it displays the image as relative to the /php/ dir, like: userfiles/image/bik.jpg
Searched a bit for a fix for this, but with no luck. Isn't there a way to make a complete path for the images?
Like: http://mydomain.com/etc/etc/userfiles/image/bik.jpg
Fri, 02/15/2008 - 00:37
#1
Re: Images shows up broken in editor
This is in PHP btw
Re: Images shows up broken in editor
$Config['Enabled'] = true ;
// Path to user files relative to the document root
$Config['UserFilesPath'] = '/admin/fckeditor/editor/filemanager/connectors/php/userfiles/' ;
'UserFilesPath' is the base (root) URL not the server path...
You need to reinsert the image to your document too as the path hardcoded during insert...
Hope this help. I am using FCKeditor v2.5.1 with Coldfusion 5.
Re: Images shows up broken in editor
Hi Kenneth,
Thanks for your response.. I already tried what you suggested, but with no result :/
When adding an image to the editor the url to the image is still
I can't seem to change the url for the inserted image in any way. I'd figure that this was a very common problem, since my guess is that alot of people try and integrate the editor in their CMS.
But any suggestions are welcome, really need to get this working
Re: Images shows up broken in editor
Re: Images shows up broken in editor
i.e.:
$Config['Enabled'] = false;
$Config['UserFilesPath'] = '/userfiles/';
$Config['UserFilesAbsolutePath'] = '';
Re: Images shows up broken in editor
What's not obvious is that relative:
means relative to the place where the config file is being run. In this instance for example:
If the folder containing your files is in another directory say
then you are looking at a relative path that looks like this
you need one ../ for every folder back to the site root from where the config file is being executed, and then the path to your images folder. That's how I see it and that is how I got it to work.
I now have an image URL that looks ridiculous ../../../../../../new_section/images/my_image.jpg and very unfriendly to those who don't know what they are doing, such as my intended users. If there is another way, say to show a url like this http://www.yourwebsite.com/new_section/images/my_image.jpg then I would very happily share it.
This is using the relative path. I don't know what the absolute path is for if it just shows broken images.