Comments for SharePoint by the Tail

Comment on Permission Work Item Types in TFS by Permission Work Item Types in TFS « SharePoint by the Tail | ARB Security Solutions

Fri, 27 Apr 2012 04:50:09 +0000

[...] SharePoint Blog Post From SharePoint Development – Google Blog Search: SharePoint development in an enterprise environment … An issue can then be turned into a [...]

Comment on Creating Profile Properties by Michael Brockman

Michael Brockman — Thu, 03 Feb 2011 20:37:00 +0000

Hi Alex,

Sorry, that’s a Using alias: using SharePointProfiles = Microsoft.Office.Server.UserProfiles;

Michael

Comment on Creating Profile Properties by Alex Talarico

Alex Talarico — Thu, 03 Feb 2011 20:23:03 +0000

the object SharePointUserProfiles isn’t resolving – where did that come from?

Comment on Cross-Site Collection Navigation by K

Thu, 30 Dec 2010 11:14:23 +0000

Great post, thanks a lot for this!
The only problem I had was with browser caching. My solution was to create a different request variable each time the Javascript called the handler so that a new response was given each time. Not sure if this is the best solution but it works..
Did you come across this problem?

Comment on Cross-Site Collection Navigation by Gene

Gene — Thu, 16 Dec 2010 08:19:55 +0000

Does this support security trimming?

Comment on Cross-Site Collection Navigation by Danny

Danny — Sun, 24 Oct 2010 18:21:56 +0000

Hi,

I tried this solution but unfortunately it didn’t work for me. I checked and I debugged the navigation.ashx in Visual Studio. And I found the error on the ‘rootNode’ variable.
..
private void GetGlobalNav()
{
try
{
//Note: PortalSiteMapProvider returns data for the current request’s site collection
var rootNode = PortalSiteMapProvider.GlobalNavSiteMapProvider.RootNode;
if (rootNode != null)
{
var nodes = PortalSiteMapProvider.GlobalNavSiteMapProvider.GetChildNodes(rootNode);
//GetSerializableSiteMap(nodes);
SerializeWrite(GetSerializableSiteMap(nodes));
}
}
..

The value of this variable is the error code that you can see it below.

An error occured while rendering navigation for requested URL: /_layouts/handlers/navigation.ashx. Exception message: Object reference not set to an instance of an object. Stack trace: at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite, Boolean allowContextSiteOptimization) at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.get_ObjectFactory() at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.GetRootNodeCore()

I didn’t use publishing template for the root sitecollection. Therefore I changed sitemapprovider in the masterpage.

..
ID="TopNavigationMenuV4"
Runat="server"
EnableViewState="false"
DataSourceID="topSiteMap"
AccessKey="”
UseSimpleRendering=”true”
UseSeparateCss=”false”
Orientation=”Horizontal”
StaticDisplayLevels=”2″
MaximumDynamicDisplayLevels=”1″
SkipLinkText=”"
CssClass=”s4-tn”/>

What do you think this error means?
How can I fix it?

Regards,
Danny

Comment on Cross-Site Collection Navigation by Paul

Paul — Wed, 06 Oct 2010 00:11:47 +0000

Thank you for the help, it looks like we have found a solution using an ajax call. Thanks again.

Comment on Cross-Site Collection Navigation by Michael Brockman

Michael Brockman — Mon, 04 Oct 2010 22:35:17 +0000

That’s strange. I have it working in both FireFox and IE. I just ran it in FF and I get a 200 OK status for the call to the handler. I’m using FF 3.6.10 and jQuery v1.3.2.

Comment on Cross-Site Collection Navigation by Paul

Paul — Mon, 04 Oct 2010 22:18:05 +0000

It does work in IE, and if you go to the ashx page directly in the browser it appears. The file is located in the _layouts folders, but not in a subfolder such as your handlers folder.

Comment on Cross-Site Collection Navigation by Michael Brockman

Michael Brockman — Mon, 04 Oct 2010 22:07:13 +0000

Hi Paul,

Have you tried it in IE? Depending on what you named your ASHX file and where it’s located (mine’s in Layouts subfolder called “handlers”) you may need to change the handlerUrl in the client script. The 401 error sounds like it’s just not finding the ASHX file.