Content Editor Links - SharePoint 2007

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.

Authentication Failure on Front End Server

If, like me you find that you are unable to authenticate to your SharePoint site locally on the server, then follow this KB article to fix http://support.microsoft.com/kb/956158/en-us

All to do with a "loop back" check apparently.

Restricting Available Site Definitions

I recently did an 'in place' upgrade from SharePoint Portal Server 2003 to MOSS 2007. After the upgrade, when trying to create a new site there was only one site definition available.

After some searching of various blogs I found that you can restrict available site definitions by going to this link http://&ltyoursiteurl>/_Layouts/AreaTemplateSettings.aspx

Here you can select which definitions to allow/not allow.

Multiple Authentication Requests - External Access

If you are accessing a WSS or MOSS site externally and not via a VPN connection, you will be asked to re authenticate whenever opening a Microsoft Office document. This will slowly drive you mad.

To overcome this first add the SharePoint site to your trusted sites, then you need to tell Internet Explorer to automatically log on using the current username and password.

Do this from Internet Explorer's menu...

Tools > Internet Options > Security > Custom Level > User Authentication > Automatic logon with username and password

You should not be asked to log on when opening documents now.

Traffic Lights

While working with clients I am often asked if they can have traffic light indicators on list items. This would be great for rag status on project based WSS sites for example. Unfortunately this is not a straightforward task, indeed 'Key Performance Indicators' are only available with MOSS Enterprise and in anycase these are overkill for many cases.

I had considered creating custom webparts to solve this but a search on the web came up with some good information. (Credit to Christopher at PathtoSharePoint)

The list or library must contain a required choice field named priority, the choices should be (1)High, (2)Normal, (3)Low.

Now create a calculated field to store the indicator. Depending on what type of indicator you would like, choose which of the following calculations to use in this field:

- Traffic light (actually a big bullet!):
=”< DIV style=’font-weight:bold; font-size:24px; color:”&CHOOSE(RIGHT(LEFT(Priority,2),1),”red”,”orange”,”green”)&”;’> •< /DIV> ”

- Indicator (reusing the default SharePoint KPI images):
=”< DIV> < IMG src=’/_layouts/images/KPIDefault-”&(3-RIGHT(LEFT(Priority,2),1))&”.gif’ /> < /DIV> ”

- Font color:
=”< DIV style=’font-weight:bold; font-size:12px; color:”&CHOOSE(RIGHT(LEFT(Priority,2),1),”red”,”orange”,”green”)&”;’> ”&Priority&”< /DIV> ”

- Background color:
=”< DIV style=’font-size:12px; background-color:”&CHOOSE(RIGHT(LEFT(Priority,2),1),”red”,”orange”,”green”)&”;’> ”&Priority&”< /DIV> ”

Now add the list or library as a web part on the page where you would like to see it and the indicator. This will look very odd and the indicator will appear as html text.

Now add a CEWP (Content Editor Web Part) to the page. Set the CEWP to hidden as you do not want to see it on the page. Using the source editor of the CEWP add the following javascript:

< script type="text/javascript">
var theTDs = document.getElementsByTagName("TD");
var i=0;
var TDContent = " ";
while (i < theTDs.length)
{
try
{
TDContent = theTDs[i].innerText || theTDs[i].textContent;
if ((TDContent.indexOf("< DIV") == 0) && (TDContent.indexOf("< /DIV> ") > = 0)) {
theTDs[i].innerHTML = TDContent;
}
}
catch(err){}
i=i+1;
}
< /script>

If everything is correct your list will appear with indicators like the above example.