Images path problems

We started using FCKEditor in our application and it works great except for a problem with the images. Our site is configured like this:

wconnect\ (this is root folder)
wconnect\graphics\
wconnect\FCKEditor\

So in our pages to display images we are using src="graphics/someimage.gif" but that does not display correctly when opened in FCK because it runs in another folder, it needs to be src="../../graphics/someimage.gif"

I tried different configurations by moving the 'Editor' folder and using the Basepath property, but I could not get it to work.

The only solution I can think of would be to move the content of FCKEditor\Editor to our site root, which I really don't like.

Any other solution/idea ? Thanks
Sylvain

Wed, 02/08/2006 - 08:28

didgiman

Joined: 26/01/2007

Posts: 130

RE: Images path problems

Your images should point to src='/wconnect/graphics/someimage.gif'

In any case, if you want to use FCKeditor to manage your images, you will have to place your images in a folder called Images (userFiles/Images; userFiles/Files; ...), because FCKeditor uploads all images to the 'Images' folder of your userFiles directory.

Wed, 02/08/2006 - 08:55

sbujold

Joined: 08/02/2006

Posts: 2

RE: Images path problems

We don't use FCKeditor to manage our images, the upload is not activated, but I want the existing HTML to display correctly in the editor.

"Your images should point to src='/wconnect/graphics/someimage.gif' "

This is using a fullpath which is not correct, that would imply a modification to all pages of our site, I don't want to use the wconnect/ folder in the paths, the default web site in the web server points to this folder. I want to use relative paths to display my images, not starting from the root.

So unless I'm mistaken, if I don't use /graphics/someimage.gif I won't be able to have the existing HTML to display correctly in the editor ?

thanks for your reply

Wed, 02/08/2006 - 09:00

alfonsoml

Joined: 31/12/2006

Posts: 3735

RE: Images path problems

you must set FCKConfig.BaseHref or the editor can't guess where the relative links should point to. (indeed it's the browser the one that parses the links, but you get the idea)