Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Could someone be so kind as to check the following in their 2010 environments.

  1. Create a doc library
  2. Turn on force check-out
  3. Turn on versioning.
  4. Add the "Edit (link to edit item)" column to the default view.
  5. Now upload a document and check it in.
  6. Use the Edit column to edit the properties.

You should see:

You must check out this item before making changes. Do you want to check out this item now?

Clicking OK, would normally check the document out and take you to the edit form (in a dialog in sp2010 if dialogs set to yes for library).

However in two environments of mine, nothing happens anymore!!!!

On live I tested tested a new library in an existing site, a new library in a new site, and an existing library in a migrated site (from 2007).

Strangely I found one document library in a migrated site which DOES STILL WORK but why this one library works is puzzling me!! The issue is new libraries don't work and that seems to confuse me more!

Again, I tried new libraries in two SharePoint environments and same behaviour.

Anyone?

share|improve this question
    
Is there anything in the ULS or Event Logs? –  Dave Wise Oct 24 '12 at 17:41
    
Nothing in ULS and assume this is because nothing is happening following clicking OK! Are you saying you don't have this behaviour? Once again I've tried in production and in development. Totally separate environments on new site collections and both don't work! –  Tezza Oct 25 '12 at 12:38
    
I'm quite surprised no one has confirmed whether they also get this issue? It may be a bug but could someone please try this for my sanity!? :) Now three environments later and same behaviour in them all for me. –  Tezza Nov 13 '12 at 17:36
    
I've discovered that in almost all cases where I am seeing a problem but there is nothing on it on the net that it means that it is an issue unique to my local environment. Either it is in the way that SharePoint is configured, custom features that are enabled or in the way that Office is configured. –  Dave Wise Nov 13 '12 at 18:04
    
Thanks but once again, three environments tried!! Not remotely close to being the same config either! Are you saying you don't get the behaviour described? –  Tezza Nov 13 '12 at 22:20
show 5 more comments

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.