OK -- maybe I have painted myself into a corner.

The page source code I am editing is in a different directory than the editor.aspx that invokes cute editor.  Now using v3.0, I was able to pre-process all <img> and <a> tag href parameters and correct them to absolute links before stuffing the source into Cute Editor.  Doing the reverse on file save, allowed the situation to be handled (in v3.0).  I, of course used, UseRelativeLinks = false and RemoveServerNamesFromUrl = false.

 

Under CEv4.0 this approach results in two problems --
1) My source with full server links and both parms true, converts the url http://lwazcc.org/web/pjohnson/images/... to http:///web/pjohnson/images/,,,,  on source entry resulting in a destroyed editor display (all image links broken) and causes the insert image popup (having set Editor1.Setting("security:ImageGalleryPath") to the appropriate value) to display the correct directory images -- but all inserted images are broken links -- http:///web/pjohnson/images/...

2) If I run using these two parms as false  the initial display has no broken links and all appears well until we insert an image.  The pop-up displays correctly but the inserted image href reads http:///web/pjohnson/images/.... and results in a broken CuteEditor display of the page.

The net of the problem is:

1) Insert images gives me broken image links for any setting of the two parms and 2) Your recommended setting of "true" destroys incoming full links.
 

Last night and for part of today your own server for the Cute Editor Web Site Demo was displaying this same problem for inserted images.  It has now been corrected.  If you can discover what was changed today (that fixed the demo) it may help me find a way out of this issue.

 

Is it possible this is a license file issue -- could the liscense be issued for lwazcc.org when it should have been issued for http://lwazcc.org ?  Just a wild idea as I am grasping at straws!