Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Feature Request: OOo should tell by which user a document is opened with writeaccess|
|Status:||CLOSED FIXED||QA Contact:||issues@framework <issues>|
|Priority:||P3||CC:||baumux, chris_mux, chrlutz, dma2002, issues, Mathias_Bauer, mux2005, piopaw, thomas.lendo|
|Target Milestone:||OOo 3.1|
|Issue Type:||FEATURE||Latest Confirmation in:||---|
Description reneksuz 2005-12-20 08:43:41 UTC
In M$ you get a message which tells you, that a document is writeprotected right now, because it is used by user X. This is an important feature for us, because different people could work on the same files. If I open a file that is opened by user X, I only get "writeprotected", but I don't know why. If OOo could tell me, by whom the document is used, I could tell user X to close the document for a few minutes. I could do my change and close it again ... Perhaps it would be possible to create a temporary file when you open a document in which the name of the user, who opened it, is stored. So every time one openes a document, OOo could check if there is a equally-named file with a different extension (perhaps document1.tmp) and could read out the username and display it to the user who wants to open the file. Kind regards, Rene Ksuz
Comment 1 thorsten.martens 2005-12-20 10:22:20 UTC
TM->requirements: please have a look, thanks !
Comment 3 piopaw 2007-07-27 20:24:01 UTC
This feature should be compatible with M$. I mean that OOo should tell if the document is open in M$ and vice-versa.
Comment 4 Olaf Felka 2007-07-27 21:37:27 UTC
"This feature should be compatible with M$. I mean that OOo should tell if the document is open in M$ and vice-versa." And why not KOffice and so on? And what is this information good for? Sounds like spyware for.
Comment 5 piopaw 2007-07-28 09:23:22 UTC
""This feature should be compatible with M$. I mean that OOo should tell if the document is open in M$ and vice-versa." And why not KOffice and so on? And what is this information good for? Sounds like spyware for." Not a spyware but groupware. We had to make regression in deployment for 700 users because lack of this functionality. Let me describe it: Deployment was for 700 workstations. 120 are LTSP, 360 are Windows Terminal Services and the rest are desktops and notebooks with Windows XP. All users are using file server based on linux with samba. For many of them the basic function is editing one document by many users i.e. spreadsheet. Of course they are not doing it at the same time but one by one. The unresolvable problem is that when someone has opened the file for editing and forgot to close it, other users couldn't make any changes and they don't know who (of possible i.e. 25 people) has locked the file. Even worse: if the file was opened by samba user, LTSP user didn't know that the file is opened until he tried to save it!!! I think for those reasons, lack of this function is a serious limitation for big deployments and in consequence for making OOo more popular.
Comment 6 Olaf Felka 2007-07-28 11:39:14 UTC
I know what is meant with the original issue: we need some kind of groupware functionality. But why do we need to know what kind of software blocks a document? That's what I would call a kind of spyware functionality. In general nobody needs to know what software I use, even not my college.
Comment 7 piopaw 2007-07-28 13:24:51 UTC
"I know what is meant with the original issue: we need some kind of groupware functionality. But why do we need to know what kind of software blocks a document? That's what I would call a kind of spyware functionality. In general nobody needs to know what software I use, even not my college." Maybe it's because of my English... I don't want to know what kind of software blocks a document. I just want OOo to recognize that document is open by another user, even if he uses M$, and OOo should mark document as blocked in the way that also M$ can recognize.
Comment 8 dma2002 2008-01-17 18:36:24 UTC
Dear developers, there are already 73 votes tabulated. Could you please set the target at least? Or there are any reasons not to do it?
Comment 9 palcons 2008-04-24 12:12:25 UTC
Comment 10 palcons 2008-04-24 12:13:53 UTC
Comment 11 Mathias_Bauer 2009-05-28 11:44:43 UTC
This is obviously fixed now in OOo 3.1.
Comment 12 Mathias_Bauer 2009-05-28 11:45:56 UTC
Comment 13 Olaf Felka 2009-05-28 11:51:40 UTC
@ tm: Please have a look. You are doing the file locking stuff.
Comment 14 Mathias_Bauer 2009-06-16 22:47:04 UTC