25 Jan 2008, 5:29 PM
|
GCB
Joined on 12-10-2007
Posts 78
|
|
|
I did download it. The behavior is different now, but it is still wrong. Now instead of changing the url to an absolute url it changes it to a relative url by adding the relative subdirectory of the page containing the editor:
For example, imagine the following scenario:
\___ \Pages Here.aspx__ \ \MorePages There.aspx
Here.aspx is in the subdirectory Pages, which is off the site home directory. There.aspx is in the subdirectory MorePages which is off the subdirectory Pages.
Inside Here.aspx I have a UltimateEditor control in which I type a link to There.aspx. I.e. <a href="There.aspx">There</a>. UltimateEditor formerly change that to <a href="http://www.foo.com/Pages/There.aspx">There</a>.
Now it's changing it to <a href="Pages/There.aspx">There</a>. But 'There.aspx' isn't in Pages, it's in MorePages.
I have written code in my CMS to change the links myself. When a relative link is found in dynamic content, I search for the page, or image, or whatever, and I dynamically make it absolute before sending it to the browser. Then when the user save the content, I dynamically make it relative before storing it in the CMS database. So the user never has to enter either an absolute or relative path for the page on the site, just the page name. This has the added benefit of allowing me modify the directory arrangment of pages without breaking anything. But I had to do this to get around the earlier bug.
So I would rather UltimateEditor not change any links at all. If your changing these links is considered a feature then such a feature definitely should be optional.
As of now I'm going to have to write more code to get around your latest change, because it breaks my CMS.
|
|
|
|
|
|
|
|
|