Image Links / HTML Editor2

[Cologne]

Hello,

when I uload an image in the backend it saves only the relative path. Thats not so good, cause then the image is not to see in the frontend.

How can I say, that the absolute path should be saved?

Or is there an other trick?

Denis

[Dani Chankhour]

To get an absolute path we will add the site http manually.

Open the fck_image.js which is located under HTMLEditor/dialog/fck_image, and on line 434 change it from:

GetE('txtUrl').value = url ;

to

GetE('txtUrl').value = "http://localhost" + url ;

You will just need to replace "http://localhost" with your absolute path.

This is a temporarily work around and i will keep looking to see if there is a better work around.

Let me know if you have any other questions.

[Cologne]

thanks dani.

hmmm, thats not so cool. I bought the extension, because i dont want to edit the source code. The upload itself works cool. But, where is the need of that html editor, if the images a stored relative?
Most use I know are CMS, ad content in the backend and show in the frontend.

Will this be fixed in a update?

Denis

[Dani Chankhour]

I have logged a bug in our bug base in regard to this issue. And we will try to get a fix for it in the next dot release.


Sorry for the inconvenience.

[Cologne]

Anything NEW here???

Will this be fixed, to save the fullpath to the image?

Denis

[Dani Chankhour]

There is a bug logged in our bug base in regard to that issue.

I'm not sure when the next dot release will be released, but the fix should be included in our next dot release. You will get an email with the issues that were fixed when the dot release is out.

[Cologne]

more than a month ago :-(

[Cologne]

The FIX, is this the answer?

Fixes addressed in this build:

- Corrected an issue that caused include file references to be incorrect when using site root relative links. Site root relative links will now properly use the 'virtual' setting.

Cheers
Denis

[Dani Chankhour]

No, that fix was related to using Virtual instead of Include when using Site Root in your DW site definition.

In regard to your issue, could you please give me an example of how the image path is shown on your front end pages and how it is suppose to show.

I just want to explain that the HTML Editor will generate an Absolute Site Relative Path, which means that it place a / at the beginning of the path to indicate that the path will start at the root of your site.


Please post back to further assist you.

[Cologne]

the problem is, that i got a backend. for example. /backend/editor.php

the images are stored. and the editor text is stored in my database. only the images path is relativ to /backend/editor.php

but the frontend is for example. /frontend/review.php

and then the images are not found.

so, it would be cool to store the absolut path to the images. NO WORKAROUND :-) in that case i could keep iRite1.

I thought with that fix that is gone.

Denis

[Dani Chankhour]

I have opened a support ticket to further assist you at:

http://www.webassist.com/mywebassist/supporthistory.php