I have 2 users, user A and user B:
A(ACL): Author, create/delete docs, write public/replicate and copy, no roles.
B(ACL): Manager, All
Form (fields):
1 multivalue Author field (and several irrellevant text fields etc.) This field contains a role used by B and the commonusername of A (A has the same canonicle name as the server) (and servername etc).
Problem:
If A creates, edits and saves the document, then she is permited to edit, change values and save infinitly.
If B edits and saves this same document that A saved first, then A is still able to see, open, edit, change and ALLOWED to save - but with 1 great difference: The changes are NOT saved. “Modified by” is still B. NO errormessages are presented and while debugging, everything seems to go smooth.
I felt I’ve tried “everything”. I even added a new “Authors” field and put the canonicle name of A into it. I’ve deleted the Querysave and Querymodechange contents (in case something there was wrong).
Changing user A to “Editor” afterwards does NOT help either! (I restarted the client, deleting the Notescache to be sure this was true).
This is not a “button-controlled” save either (all though it could be). The problem exists upon even just opening in Editmode, changing some contents, and then pressing -S. It still does not save A’s changes!
Subject: Author unable to save document after being saved by Editor+
“If B edits and saves this same document that A saved first, then A is still able to see, open, edit, change and ALLOWED to save - but with 1 great difference: The changes are NOT saved.”
But user B is still able to save the document? Usually this kind of behaviour is possible only, if the document contains a SaveOptions item set to “0”. Just to be absolutely sure, check in the items list of the doc (from a view, not when the doc is opened) and make sure that no SaveOptions item exists.
Subject: RE: Author unable to save document after being saved by Editor+
You guided me to something I didn’t think of, and it seems you are on to something. Upon opening the document, I have a “SaveOptions” value of “1” (due to a 3rd party software computed subform I am using) that I didn’t think of checking for this field. But from the view level I have a “SAVEOPTIONS” field with a value of “0”. I don’t understand this change, but as far as I can see it looks like 2 different fields to me. But nevertheless, upon opening the document, the “SaveOptions” value is “1”, so why is this “view-based” - “SAVEOPTIONS” value (of “0”) overthrowing the document “SaveOptions” value?
Can this behavior be related to the ACL which I explained in my initial post? If so, why, whats wrong with it, and how do I fix it?
Subject: RE: Author unable to save document after being saved by Editor+
Kenneth, it’s actally the same field (or item, to be more precise). Probalbly within that subform resides some logic, that changes SaveOptions to “1” when you open the document.
And when I say “you”, I mean “you”. The item value is NOT changed to “1”, when the suspicious user opens the document and that’s the whole secret.
When you look in the document properties from the view level, you see what is actually saved to disk. As soon as you open the document, any kind of changes might have already occured to the doc, but not necessarily changes that get saved back to disk.
You have to find the code that changes the value of SaveOptions when opening the doc, might e.g. be in QueryOpen or QueryModeChange and so on.
Subject: Author unable to save document after being saved by Editor+
What do you mean by “A has the same canonicle name as the server”? This could be where your problem lies? How is the ACL of the database set up with respect to User A and the server.
BTW you should always use the full canonical name of a person in readers and authors fields, otherwise they don’t work consistently. Your document may be getting confused because it has 2 authors fields: one with the common name and one with the canonical name. Stick to canonical name! User B doesn’t need to be in the author field if they are an editor - has no effect.
Check the contents of the field in document properties: Authors should be READ/WRITE ACCESS NAMES and canonical name should be “CN=User A/O=MyOrg”.
Check allow multiple values checked if more than one entry in your field.