'Item is locked by you' next to new content

[mcmagi]

After an upgrade to the 7/13 nightly build, I noticed some new behavior in Alfresco.  Suddenly, next to all newly created content, a lock icon now appears with the mouse-over text "Item is locked by you".  Content Contributors can now no longer submit content that they have entered to the workflow because of this lock icon.  However this lock icon does not prevent Content Managers from entering and submitting new content.  Is this new functionality that I am unaware of, a configuration issue as a result of the upgrade, or a bug?

Also, I noticed by reverting to 2.1 RC1 that the problem does NOT go away, which is odd because it did not happen when I first upgraded to 2.1.

Thanks!

- Michael C. Maggio
   NCS Technologies

[alarocca]

Kevin, thanks a lot for the information.

Regarding 2.1, is there a way to enforce locking via CIFS for all users? If this is not possible chancing properly any configuration file, could you point me at the right source files where I can do it?

Best regards,
Alessandro

[kvc]

Yes, locking has been supported since 2.1.0 Community.  Official support for turning on locking via CIFS came with 2.2.0E, where we were able to certify.

To configure locking behavior in CIFS, you can modify our Spring config file network-protocol-context.xml to use AVMLockingAwareService by changing bean reference from
indexingAVMService to indexingAVMLockingAwareService.  AVMService is the underlying API for all AVM content operations; AVM locking-aware service is a wrapper around
AVM service to enforce all locking behavior (you can use either depending on what your application's needs are).

Kevin

[alarocca]

Thank you Kevin. I changed the only reference I found within that file but unfortunately nothing seems to be changed. If I open a document via CIFS, the web client does not show any lock allowing user to edit or checkout that file.

   
<!– AVM Filesystem Interface –>
   <bean id="avmDiskDriver" class="org.alfresco.filesys.avm.AVMDiskDriver" >
<!–
     <property name="avmService"><ref bean="indexingAVMService" /></property>
–>
     <property name="avmService"><ref bean="indexingAVMLockingAwareService" /></property>
      <property name="transactionService"><ref bean="transactionService" /></property>
      <property name="authenticationComponent"><ref bean="authenticationComponent"/></property>
      …
‍‍‍‍‍‍‍‍‍‍‍

I don't know if there are differences, but I need locking enforced on a filesystem (as defined within file-servers-custom.xml) rather than on an avmfilesystem (disabled on my installation).

Any hint?

Best regards,
Alessandro

Yes, locking has been supported since 2.1.0 Community.  Official support for turning on locking via CIFS came with 2.2.0E, where we were able to certify.

To configure locking behavior in CIFS, you can modify our Spring config file network-protocol-context.xml to use AVMLockingAwareService by changing bean reference from
indexingAVMService to indexingAVMLockingAwareService.  AVMService is the underlying API for all AVM content operations; AVM locking-aware service is a wrapper around
AVM service to enforce all locking behavior (you can use either depending on what your application's needs are).

Kevin

[kvc]

Alessandro:

This configuration change I noted only works for the AVM mount point and content you create, edit, and delete within an AVM store (a user sandbox).

Within the SpacesStore (the default store for general document management and collaboration), there is not a corresponding locking service.  Instead,
you need to configure rules to auto-checkout items you create or modify (not deletes; deletes in the AVM are considered file modifications that are
versionable and can be sync with other local (staging) or remote (live) stores and recovered via revert or rollback). 

Hope that helps.  This is known to work in 2.2.0E (it was certified) but there was no code changes necessary to enable from 2.1.0C.  I can't guarantee
that is does work, however, although if there was a minor fix I missed between 2.1.0C and 2.2.0E, your best bet will be the upcoming Community
release this June which catches our Community codeline up with all our latest maintenance fixes.

Kevin