sorry, but a variation of the problem seems to be there again;

1) open the example Relative-or-Absolute-URLs.aspx
2) now insert a link to some file, downloads/test.jpg for example;

3) post -> the link points to /downloads/test.jpg

4) switch to htmlview, switch back to normal view;

5) post again -> the link points to http://cutesoft.net/example/downloads/test.jpg

this is a problem for me, the reasons r 2:

a) my application architecture

 my folderstructure:
 /app
    show.aspx (writes the content to the user)  
    /images
    /downloads 
    /maintenance
       /cutesoft
       /downloads (is a virtual entry pointing to ../downloads)
       /images (is a virtual entry pointing to ../images)
u see, the editor is placed in another folder than the aspx which puts the content to the website; to overcome the problems, all linked data (images, downloads) is placed in two folders which are referenced by virtual entries in the maintenance app, so /downloads/test.jpg is valid for the maintenance app and for the website itself;

if sb saves his stuff in normalview after switching the links point into the maintenace folder, which may be valid as links but leads to problem as normal visitors have no right to access data in the maintenance folder;

b) when using anchors in the page the output of cute editor is simply wrong;
for example, my link points to #top; save it and open um switch to html, back and save; and now the link points to http://cms/maintenance/#top which is simply wrong;

and .. no, the workaround to set the link to show.aspx#top does not work, because show.aspx gets many more parameters (displayed menus and so on) and i don't think my user would be very happy if they had to know my app-architecture just to edit their content :-))


p.s.:
if u switch back to html and save, the link is corrected in the samples downloaded with cuteeditor; but this doesn't work online