I have a site that is extended for use externally. The links that are used insite of a content editor web part (CE) do not work externally.
What I noticed is that when a link is clicked it resolves to http://servername/linkxxxxx and not http://extranetaddress/linkxxxxx as expected.
This result occurs even when the link entered into the CE is trimmed to just /linkxxxxx. I am surprised at this behavior as in all other areas, for instance, quick launch items, the links are managed correctly.
One fix that I found works, is to edit the source in the CE web part and remove the http://servername part, instead of removing this part using the rich text editor. After doing this, every works correctly.
The problem with this fix is that every previously created link will have to be manually dealt with after extending a site and also content editors will need extra training to show them how to deal with the issue.
I found that the problem only occurs when using an extended site and a host header, so I have implemented a better fix using AAM (Alternate Access Mapping).
Firstly I removed the extended site from IIS and then added extranet.co.uk as an AAM for the extranet zone. This is done within Central Admin.
All now works correctly.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment