SharePoint 2010 Breadcrumb

From my perspective, this approach is difficult to use because it is hidden from the user. Once you know about it the breadcrumb is easier to find, but its nowhere near as usable as a traditional breadcrumb.

Smashing Magazine offers a range of alternatives you can consider in implementing your own breadcrumb which are worth considering if you want to create a fully-customised master page.

However, want if you want a breadcrumb of the same style as SP2007?

What if you want to revert the 2010 breadcrumb into the style of the 2007 breadcrumb? Well it turns out that the v3 masterpage(the 2007-style masterpage that runs on SharePoint 2010 to allow companies to avoid a visual upgrade) runs the old-school masterpage.

If you dive into the v3 masterpage (default.master) you can see the following snippet to in place of the breadcrumbs.

<asp:SiteMapPath SiteMapProvider=”SPContentMapProvider” id=”ContentMap”  SkipLinkText=”" RenderCurrentNodeAsLink=”true”  NodeStyle-CssClass=”ms-sitemapdirectional” runat=”server”/>

As it turns out, if you paste that snippet into the v4 masterpage it will work perfectly.

If you try to install AD and DNS onto a Sharepoint VM after having already installed Sharepoint you run into a range of problems. The first time I tried to fix the problem I fried my environment and had to revert to a snapshot.

First, install AD and DNS as you normally would. Here’s a link to the guide I used.

At this point if you try to hit your Central Administration site or any other Sharepoint site, you’ll get a Service Unavailable message on any page you hit.

I tried the following to bring up something, anything Sharepoint:

• Hitting my server via the computer name (http://phoenix:5555)
• Hitting my server via the IP address (192.168.0.2:5555)
• Hitting my server via localhost (http://localhost:5555)
• Hitting my server via the fully qualified domain name (http://phoenix.kmtests.local:5555/)

None of these works, and if I wasn’t getting the Service Unavailable message, I was getting one that said:

Under Construction

The site you are trying to view does not currently have a default page. It may be in the process of being upgraded and configured.

Looking at the server logs, you see two errors:

Application Log Screenshot

System Log screenshot

Aha! Adding a domain to the mix changes all the user accounts so that your old accounts need to be reconfigured. This is easily done by going into IIS Manager and updating the Identities of all of the app pools to reflect the new, domain enabled accounts.

i.e. servername\MossServiceAcct becomes domainName\MossServiceAcct

Having reconfigured the app pools, trying to hit the server again give you a message that says

The current identity (domainName\MossServiceAcct) does not have write access to ‘c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files’.

You can resolve this easily by navigating to that location and by granting write access to the folder in question (you will need to do this for each unique service account which hits the Temporary ASP.NET Files folder).

Central Admin will loads, but hold on cowboy/girl, you won’t be able to get to any of the pages on the Operations or Application Management tabs.

Some or all identity references could not be translated.   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)

Will it never end?

Ultimately I followed the process outlined on two specific web pages (retyping them would be silly)

• WSS & SharePoint Server 2007 Password Change via STSADM by Joel Oleson
• How to change service accounts and service account passwords in SharePoint Server 2007 and in Windows SharePoint Services 3.0

Following Joel’s tips I got 100% of the way, but the other page a good reference anyways. I found that there were so many passwords to re-enter that I missed a couple (specifically the stsadm -o editssp command) but got there in the end.

Good luck, it’s a painful process, but a possible one. Just be careful and meticulous and you should be okay.

It is impossible via the browser (from what I can see) and via designer it is far from obvious how to accomplish this. What you need to do is open the workflow in Sharepoint Designer, click “Finish” and the workflow will re-attach itself. Not very obvious, but it works.

Unfortunately there is no way to associate a workflow with another list unless you open the various workflow xml files change the list guids inside.

My setup:

Most people doing Sharepoint development will be doing so in a proper networked environment (setup by a proper network admin).   In which case this article is unlikely to apply to you and this article, can probably point you in the right direction (hint: you need to set your web.config proxy settings).

I am running a Sharepoint development environment at my house, using VMWare, with a minimal win2k3 setup.  I’m not a server admin and I’m conscious hits to performance so the environment is very lightweight.  No Domain Controller, no Active Directory.  I’m a developer not a sysadmin.

The problem:

Unfortunately, Sharepoint cares not for my developing ways and when I tried adding an RSS webpart to a Sharepoint page got the following on-screen error:

An unexpected error occured processing your request. Check the logs for details and correct the problem.

Crapola.  First I thought dodgy rss.

Nope.

Then I thought, the IIS account doesn’t have web access.

Nope.

So then I looked at the million and one “Sharepoint rss proxy” articles on Google  to no avail.  They all want you to make changes to the defaultProxy entry in your Sharepoint’s web.config.

Nope.

The cause:

For some reason, if you don’t have a proxy setup, Sharepoint throws it’s toys out the pram and won’t work.  It won’t even try to make a network call (I checked using WireShark).  Even when I tried to tell the defaultProxy entry to bypass all addresses, it ignored me.

The solution:

Setup your own proxy.  It’s actually very simple (trust me I hate server admin stuff)

• disable Windows firewall (should have a firewall on your host anyways)
• I then followed the instructions on support.microsoft.com as best I could under the “Installing the Routing and Remote Access Service” heading.
• Then magically my rss webparts worked

Also important is to make sure you use a proper RSSViewer part instead of a RSSAggregatorWebPart (added manually).  The only difference I can see is in the configuration xml, but the latter continued to break even after my changes.

Hopefully this doesn’t up some insane hole in my firewall.

Hope that helps.

It’s also good to know the full retail price is £20 less than the 8gb iPhone 3G and £120 less than the 16gb iPhone 3G.

I’m definitely looking forward to seeing this phone.

Update Jan 26: Looks like Nokia has come out and stated that March 31 IS NOT the official release date.

“Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.”

How helpful.

The issue is the dataview has a hard-coded reference to the list guid on the original site. To resolve this, simply wrap curly braces “{” and “}” around all instances of the guid. This tells Sharepoint to refer to the newly created list when deploying the site template.

Granted this seems like a bug, but it works.

There should be 6 or 7 references to the listID in any dataview. Just hunt through the code and you should find it fairly easily.

One of the most challenging aspects of building SharePoint-enabled web parts is using JavaScript to interact with specific controls. As a consequence of how SharePoint renders controls with id’s in Sharepoint WebParts, it’s near impossible to write clean JavaScript.

From a maintenance perspective I HATE using server-side code to render JavaScript. It’s inelegant and reeks of a lack of forethought. Yuck yuck yuck. It’s like sweeping dust under the rug.

Wherever possible, webpart-specific javascript should be held within a single .js file (stored in the 12Hive). The problem is that Sharepoint alters a control’s ID during the page rendering process.

So, a label with the ID “label1” might become “ctl00_label1”. The naming process is entirely unpredictable.

This makes interacting with a specific DIV, INPUT or any other html element very difficult because you can’t predict the rendered IDs during development. This is especially problematic if you’re looking to host several instances of a webpart on a single page.

One really terrible way of dealing with this is to render the html yourself by adding literal controls ala

	LiteralControl l = new LiteralControl();
	l.text = “
blah
”;
	this.Controls.Add(l);

To tackle the problem I’ve devised the following solution which revolves around creating a Javascript class to accompany the web part:

• create properties to store the dynamically generated IDs of every html component to wish to interact with
• create pointers to every html component you wish to interact with
• create an init function. As input you pass the clientID of the webpart AND the id’s of every component you wish to interact with.

• this function will store the id’s using the properties
• this function will also attach the pointers to their respective objects
• this function should also attach any eventhandlers
• create any supporting functions (i.e. webservice calls, webservice receivers)

This approach embraces the absence of reliable identification info. It is also sympathetic to having multiple copies of a webpart on the same page.

Here’s what the javascript might look like

function UpdatingLabelWebPart()
{
	var me = this;	//required to reference the object at runtime
	this.clientID = null;	//ids
	this.labelID = null;
	this.buttonID = null;
	this.label = null;	//controls
	this.button = null;
	this.register = function (clientID, labelID, buttonID)
	{
		me.clientID = clientID;		//init the id
		me.labelID = labelID;
		me.buttonID = buttonID;
		me.attachToButton();
	}
	this.attachToButton = function()
	{
		//if the controls haven't loaded yet
		if (document.getElementById(me.buttonID) == null || document.getElementById(me.labelID) == null)
		{
			setTimeout(me.attachToButton, 50);
		}
		else
		{
			//register the controls
			me.label = document.getElementById(me.labelID);
			me.button = document.getElementById(me.buttonID);
			//attach any events
			button.AttachEvent("click", me.buttonClicked);
		}
	}
	this.buttonClicked = function(sender, args)
	{
		me.label.innerHTML = "Hello World";
	}
}

Then in your webpart you write a teeny tiny bit of javascript which you register as a clientscriptblock.

String myScriptBlock = String.Format(@"
					var tmp = new UpdatingLabelWebPart();
					tmp.register('{0}','{1}','{2}');
				    ", this.clientID
				    , this.label1.clientID
				    , this.button1.clientID);
Page.ClientScript.RegisterClientScriptBlock(typeof(Page), "UpdatingLabelWebPartJS",myScriptBlock, true);
Page.ClientScript.RegisterClientScriptInclude(GetType(), GetType().ToString(), "_layouts/1033/myJS/UpdatingLabelWebPart.js");

This approach lets you have multiple instances of the same AJAX-enabled webpart and saves you the hassle of having to write annoying javascript (having to write me.label is hardly a chore).

Some background:

• My project namespace is ajaxTest
• My webservice class is helloTest
• My webservice function is helloWorld

I enabled the web service using the [System.Web.Script.Services.ScriptService()] attribute

I put the script manager code block in place and included a reference to the service.

<asp:ScriptManager ID=”ScriptManager1″ runat=”server”>
<Services>
<asp:ServiceReference Path=”helloTest.asmx” />
</Services>
</asp:ScriptManager>

I then created some javascript to call the web service

function testScriptService()
{
var tmp = helloTest.helloWorld(onResult, onTimeout, onError);
}

It was at this point I received the “helloTest is undefined” message.

A quick search on google revealed two websites which helped me.  The first had the right answer (in my situation).  Strangely, the second website had a slightly different solution which seems to have helped a number of people, but I was unable to figure out why (I didn’t work for me).

So, the solution that worked:

You need to fully qualify the javascript with the namespace of your webservice.

Namespace.Class.Function >> ajaxTest.helloTest.helloWorld

The solution which didn’t work for me but has worked for others is to use the following structure:

Namespace.Services.Class.Function >> ajaxTest.Services.helloTest.helloWorld

No idea why the difference, but hey.

Credit where credit’s due, thanks to Omen’s blog and Ryan at Solutek.