Coordinator should and is able to delete file using WebDAV, the file disappears from WebDAV and FTP (even after new login), but it is still available in Alfresco Share and Alfresco Explorer (not only visible, even its contents is available). The same applies for Collaborator and Editor. They shouldn't be able to delete contents created by other users, but they're using WebDAV, the file disappears from WebDAV and FTP, but it is still available in Share and Explorer.
However, this problem doesn't occur on the default empty database and contentstore. We can reproduce it only using our data. The same installation of Alfresco 4.2.c was used for testing in both cases (with empty initial data and our data).
Nothing is logged into catalina.out, alfresco.log or share.log after deletion from WebDAV.
We're installing Alfresco as a custom installation into Tomcat using alfresco.war and share.war from alfresco-community-4.2.c.zip. Only the .properties files are customized, the only is exception is file alfresco/WEB-INF/classes/alfresco/authority-services-context.xml, where the property adminGroups is extended to a specific role from LDAP.
We tried to compare database dumps before and after usual deletion from Share to see if there can be seen something obvious in the database (some deleted column that could be missing, for instance), but with no luck. We cannot provide our data because of security (and their size), but if you need any other information (like the diff file of two successive database dumps before and after deletion), we can provide it.
This problem could lead to security issues when deleted files can become still visible to some users. Does anybody have similar experience or an idea how to fix this? I tried to open a bug report on issues.alfresco.com, but I was advised to post on forum because the problem is not reproducible on fresh Alfresco installation: https://issues.alfresco.com/jira/browse/ALF-17663
I think this is still an open bug, despite if it is reproducible on a fresh alfresco or not. I still have it on alfresco 4.2.c . Do you accept bugs only on fresh alfrescos? Is this bug correlated to the bug MNT-8704 in jira?
