Access problem to document library

[alberto]

Hello,

I'm giving share a try and I'm finding a problem.
I have created a site and I invited some users. Two of the users do not have a problem accessing the site, uploading files and so on. However, there is another user that, even though he can participate in discussions, read the wiki. etc, he gets an error when trying to access files. The curious part is that he can see the folder in Document Library but he gets this error in the recently modified files:
Wrapped Exception (with status template): Failed to execute script '/org/alfresco/slingshot/documentlibrary/doclist.get.js (in classpath store file:/opt/alfresco/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/templates/webscripts)': Access Denied. You do not have the appropriate permissions to perform this operation.
He also gets this error when accessing the folders in the document library.
Of the three users one is site manager and the other two are site collaborators (one of then has the problem)
Any ideas?

[vamsi_reddy]

Hi,

I have the same problem. Does anyone have a solution to this issue?

Thanks,
Vamsi

[alberto]

Update.
Strangely enough, the user can upload documents but he can not access them afterwards.

[mikeh]

How were these users created? Also, if you use the Explorer interface (at /alfresco) is there anything strange in the permissions for the Site or documentLibrary spaces?

thanks,
Mike

[alberto]

Users were created from web client. Afterwards, they were invited from share.
Permissions are set as contributors in share. Everyone has a coautor role in sites (which is the default I believe)
If you log in into the web client with the problematic user you can access the files in the sites/nameOfSite/documentLibrary
The only difference with respect to a base setup is that share is intalled in a different machine than alfresco. However, the other two users can access the documents. And, in fact, the problematic user can upload documents but he gets the above error when trying to browse through the library.

[alberto]

I've found the problem 
We had put in the library a couple of links to files in the repository. We did this by using the web client (we know is not the correct way but we are testing). The main reason to take this route is to not have certain files repeating all over the repository. For example, when we have specifications for a material that is present in different projects it makes no sense to copy it every time. Thus, we put  two pdf's as links. The problem is that they reside in a directory for which this particular user has no rights. So, it makes sense that he could not see the files (this is what happened in the wed client), what I'm not so sure is that it makes sense to have an error instead of just not seeing the file. The problem with the actual approach is that the user can not even access the files he is entitle to. Just IMHO.