Microsoft felt it necessary to do far more work than necessary to fix the ribbon div to the top of the window. Here’s a pure CSS solution that bypasses SharePoint 2010′s default JavaScript-based approach.
Microsoft felt it necessary to do far more work than necessary to fix the ribbon div to the top of the window. Here’s a pure CSS solution that bypasses SharePoint 2010′s default JavaScript-based approach.
So there I was, minding my own and pooting forth the little green rosettas on a branding solution for a publishing site, when I encountered the following White Screen of Death error:
“Trying to use an SPWeb object that has been closed or disposed and is no longer valid.”
Take the following line out of your version of application.master, and our mystery error will take its ball and go home…
While the description field available in SharePoint’s Navigation Settings is rendered, by default, as a handy tooltip on each menu link, there was no evident configuration in which the description could be written to the screen as per my requirements.
On your way to branding a public-facing SharePoint 2010 site, you may at some point find yourself eye-to-eye with its bare, unfeeling, and unskinnable default login page. If you should find yourself facing such a task, do not panic. Rather, reach slowly for Visual Studio 2010 and follow along at home–we’re going to build a Forms Login Web Part that can handle the same authenticatory task in much more design-friendly surroundings.