Apache OpenOffice (AOO) Bugzilla – Issue 111704
Shared BASIC modules can be edited / Yield unexpected errormessage
Last modified: 2010-07-07 06:16:09 UTC
The fix for issue 111453 uncovered a problem that shared modules can be edited. This appears to work until the user tries to close the application, in this instant an errormessage appears warning about not being able to write the changes.
ab->jsk: According to my tests and as described in issue 111453 shared modules usually are *not* editable. The only problem that has been uncovered is the fact that modules that have been made read only on file system level still can be edited. But users can cause any kind of damage to the Office installation on file system level. We have no chance to handle all this. Please give a step by step description how to run into this pro- blem without manipulations on file system level. Otherwise I see this as P4/OOo Later or even WONTFIX.
jsk->ab: I agree with you in so far as the file access rights have indeed been modified in an unusual way. And this is not an error we have to handle, really. However, what confuses me is the fact that we even try to write the library on program exit. And this appears to happen no matter if the library has been modified or not. This shows that the office has no idea what state the library is in. So this is really about having an unclean library management, the design (if there has ever been one) is broken. Even though i can easily imagine how this happened i do not necessarily have to agree with the way things have been implemented, it's unclean.
ab->jsk: I still miss a clear description what a user has to to to get a problem. The step by step list from issue 111453 is not acceptable as it includes manipulations on file system level. Concerning the modification problem, we already have issue i104876. Please check if this is a duplicate.
Don't want this issue, closing.
.