.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Ribbon not appearing when versioning switched off

Posted By:      Posted Date: September 06, 2010    Points: 0   Category :SharePoint
Hi, I have a number of publishing sites where the versioning is switched off and does not require check out for pages.  When 'Require Check Out' is true, the ribbon appears as usual (with the Page tab, edit and Browse) and clicking on Edit Page in Site Actions also shows the Page tab of the ribbon.  However, when 'Require Check Out' is false, the ribbon (with the Page and browse tabs, and the edit icon) do not appear.  When clicking on Edit Page in Site Actions, the page does go into edit mode, but the ribbon doesn't appear. Is there a way around this?  If I switch off the publishing feature, editing then saving the page causes a SPListItem error (this appears to be related to having the publishing feature switched off on what was a publishing site).  The end users do not want the complication of versioning or checking in/out. We are using SharePoint 2010 and the web app has been upgraded from SP2007. Thanks Sandra

View Complete Post

More Related Resource Links

Creating Dialogs and Ribbon Controls for SharePoint 2010

SharePoint 2010 provides new user interface components, such as server ribbons, and the new dialog platform. As a developer, you can create controls for the server ribbon and dialog boxes for the dialog platform.

Foundations: Versioning Workflows


Developers often struggle with versioning workflows and their related classes. Matt Milner discusses the core issues related to workflow versioning and provides recommendations for making changes to workflow definitions, activities, and workflow services.

Matthew Milner

MSDN Magazine May 2009

RibbonX API: Extend The 2007 Office System With Your Own Ribbon Tabs And Controls


If you want to create your own professional looking tabs and controls in Office, check out the RibbonX API of the 2007 Microsoft Office system.

Eric Faller

MSDN Magazine February 2007

.NET Zero Deployment: Security and Versioning Models in the Windows Forms Engine Help You Create and


Windows Forms applications solve many of the problems inherent in building Web applications the old fashioned way?with HTML. To demonstrate the use of Windows Forms over the Web, the author takes his existing app, Wahoo!, and ports it to Windows Forms. In doing so, he discusses versioning, linked files, security, storage isolation, the deployment model, and everything else you need to get started building your own Windows Forms apps for the Web.

Chris Sells

MSDN Magazine July 2002

More Versioning Fun With Optional Arguments

In my last blog post , I covered some challenges with versioning methods that differ only by optional parameters. If you haven't read it, go read it. If I do say so myself, it's kind of interesting. ;) In this post, I want to cover another very subtle versioning issue with using optional parameters. At the very end of that last post, I made the following comment. By the way, you can add overloads that have additional required parameters. So in this way, you are in the same boat as before. However, this can lead to subtle bugs. Let's walk through a scenario. Imagine that some class library has the following method in version 1.0. public static void Foo( string s1, string s2, string s3 = "v1" ) { Console.WriteLine( "version 1"...(read more)

Versioning Issues With Optional Arguments

One nice new feature introduced in C# 4 is support for named and optional arguments . While these two features are often discussed together, they really are orthogonal concepts. Let's look at a quick example of these two concepts at work. Suppose we have a class with one method having the following signature. // v1 public static void Redirect( string url, string protocol = "http" ); This hypothetical library contains a single method that takes in two parameters, a required string url and an optional string protocol . The following shows the six possible ways this method can be called. HttpHelpers.Redirect( "http://haacked.com/" ); HttpHelpers.Redirect(url: "http://haacked.com/" ); HttpHelpers.Redirect( "http...(read more)

Web Part Versioning and Deployment (properties only)


Suppose I have a 3<sup>rd</sup> party Web Part (source code provided, with Web Part deployed as a Feature) that’s installed and used in several Sites within a Site Collection.  I want to make changes not to the source code (which would require updating the assembly and deploying the changes as an updated Feature/Solution Package), but to property values of the Web Part that exist.  Say the WP exists on 10 pages, and I want to change the WP’s Title property from “Amazing Vendor Web Part” to “My New Title”.


First, would this be considered an “out-of-band” patch?  Not that it matters terribly how to label this…


Second, would the ideal approach be to simply add code within a Feature Receiver in that Web Parts VS project (the Feat

SPGridView Not Appearing When Rows Exist


I have added the contents of a DataTable to an SPGridView control.  When there are no rows in the DataTable it shows the message "There Is No Data" which is correct. 

When there are rows in the DataTable the SPGridView does not appear at all.

What could the issue be?

The code is below:

DataTable gridTable = new DataTable();
gridTable.Columns.Add("Assigned To");

queryDPM.ViewFields = "<FieldRef Name='AssignedTo'/>" +
					  "<FieldRef Name='RequestDPMReviewerComments' />" +
					  "<FieldRef Name='WorkflowOutcome' />";

sQueryStr = "<Where>" +
				 "<And>" +
					"<IsNotNull>" +
					 "<FieldRef Name='RequestDPMReviewerComments' />" +

Unable to Edit the properties of a document using the ribbon


I have created a new web part page and added a document library to that page.  In the ribbon the "Edit Properties" icon is enabled and I can edit the document properties.

When I add another web part to the page and go back to select a document, on the ribbon the "Edit Properties" icon is no disabled.  I can still edit the document using the context menu of the document.

Permissions on the library did not change when I added the additional web part.  The only change to the page was adding an additional web part.

If you have SharePoint Document Versioning Enabled, do you also use the retention settings?

I am looking for stats on how many environments are out there using document versioning in there libraries but are perhaps not selecting the retention settings. (e.g. "Optionally limit the number of versions to retain" section) This as we all know in SharePoint is a major cause of database growth.
Tony Parker, MSCE . MCTP. MCITP "Anything worth doing, is worth doing right"

Quick Note: Working with the SharePoint 2010 Ribbon User Interface

Learn to extend the Microsoft SharePoint 2010 ribbon by adding a custom button that executes server-side code.

Displaying the Server Ribbon and Site Actions Menu on Customized Search Pages Upgraded to SharePoint

Learn how to add the Site Actions menu and SharePoint Server ribbon to SharePoint Server 2007 search pages that you upgrade to SharePoint Server 2010 by using visual upgrade.

Video: The Ribbon User Interface in SharePoint 2010

This demonstration shows the SharePoint 2010 Server Ribbon. (Length: 2:37)

Video: Developing Ribbon Controls in SharePoint 2010

This demonstration shows how to create ribbon controls for SharePoint 2010. (Length: 3:08)

Localization for command text Microsoft Ribbon for WPF

Hello, Is there any way I can localize the command text that comes with the ribbon, like the commands in the Ribbon context menu?   Add to Quick Access Toolbar Add gallery to Quick Access Toolbar Remove from Quick Access Toolbar Show Quick Access Toolbar above the Ribbon Show Quick Access Toolbar below the Ribbon Minimize the Ribbon Maximize the Ribbon   I got this list from the Source -- \Resources\ExceptionStringTable.txt

WPF Ribbon theme customization

Hello everybody!   Is it possibile to customize the builtin wpf ribbon themes?   Thank you very much!

Microsoft.mshtml / mshtml.dll versioning and reference issues

Hi, Couldn't find a more relevant section to put this in, so I'll throw it here as I'm coding in C#, although that doesn't really matter. I'm using .NET 4, trying to add a reference to mshtml, and I want to have all the capabilities depending on the version the client has installed. If I add a reference to the COM component called 'Microsoft HTML Object Library', the reference is labelled "MSHTML" and the path points to an assembly in the GAC called 'Microsoft.html' for some reason. Even though I have IE8 installed, it is still missing the IE8 interfaces, which makes me think it is just pointing to the Microsoft.html.dll wrapper instead of generating the reference from the actual COM compoment. The Microsoft.html.dll wrapper is missing the IE8 interfaces, and from what I can tell, this wrapper is somewhat unnecessary with the .NET 4 "Embed Interop Types" feature. The other thing that scares me is the "Specific Version" field on the reference, which is set to true, and I can't change it. What if someone has a lower version of "Microsoft HTML Object Library" than my dev machine? EDIT: Sorry, got a little confused between adding a reference to Microsoft.mshtml .NET assembly and directly to the COM component.  If I add the reference to the COM component, "Specific Version" isn't available in the properties, bu
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend