I don't think the issues with StripAbsoluteAnchorPaths set to false are
going to matter if you use AnchorPathToStrip. I will try to explain a bit further - if you have StripAbsoluteAnchorPaths set to true and AnchorPathToStrip
is not set, the editor will try to make the shortest path possible from all URLs. For example, you are on the page http://server/pages/default.aspx
and you insert a link to http://server/pages/test.aspx
. The editor will shorten the URL and make it just test.aspx
, because the rest is the same as the current page. This works in normal ASP.NET sites but will fail in MOSS 2007, because the server will not be able to validate the URL "test.aspx". That is why we recommend that you set StripAbsoluteAnchorPaths to false - this way the editor will not change the original URL http://server/pages/test.aspx
and the server will validate it.
When you have StripAbsoluteAnchorPaths set to true and AnchorPathToStrip
is set to some value, e.g. "http://server", then the editor will use this value to modify the URL http://server/pages/test.aspx
and will produce /pages/test.aspx
, which will validate correctly on the server. I hope this explanation helps.
the Telerik team
Check out Telerik Trainer
, the state of the art learning tool for Telerik products.