The Content Editor Web Part provides the user the hability to build content in a more free way (within the Web Part’s capability), but it can also result in some troublesome issues.
If the scenario you are building for the MOSS internet site has a Web Application extended (to provide internal and external access to the same information, internal to content management and external to view information), then you must be warned that this web part saves the address where the content management is done, let’s look at a practical example:
If you have http://website:100/ has your internal site for content management and the http://website:80/ for the external access, then you will provide Content Managers the first address for them to work.
When the User that is performing the content management uses the Content Editor Web Part in the internal address (http://website:100/) every reference to aURL within the site will be set for the address with the 100 port. This will mean that for users in the external addresss (http://website:80/) when they try to see the information in the Web Part they will be asked for authentication.
This is a known issue and there are some workarounds available:
- Remove references to server and leave relative paths
- Activate Publishing features and replace the use of this Content Editor Web Part with the Publishing Control RichHTML, but this will prevent the user of using the Web Part advantage.
- Use third party product, like Telerik’s solution – RadEditor
- Finally, develop code to perform the first option (Dan Attis solution)
This can be a very annoying subject especcialy if your client is the one to identify this issue . . .