This repository has been archived by the owner on Jan 3, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Role and license acceptance becomes out-of-sync when initializing a revision #138
Labels
Comments
I think this has been fixed. You'll need to verify, @pumazi |
Looks like this has been partially fixed. However, we are still out-of-sync with the acceptance boolean value and end up paving over the existing one. |
mmulich
added a commit
that referenced
this issue
Dec 10, 2014
This corrects and issue where a revision would not sync up previously accepted values into the newly created content.
mmulich
added a commit
that referenced
this issue
Dec 11, 2014
This corrects and issue where a revision would not sync up previously accepted values into the newly created content.
mmulich
added a commit
that referenced
this issue
Dec 11, 2014
This will sync the license acceptance with publishing when a revision is created.
Merged
mmulich
added a commit
that referenced
this issue
Dec 11, 2014
This corrects and issue where a revision would not sync up previously accepted values into the newly created content.
mmulich
added a commit
that referenced
this issue
Dec 11, 2014
This will sync the license acceptance with publishing when a revision is created.
mmulich
added a commit
that referenced
this issue
Dec 11, 2014
This corrects and issue where a revision would not sync up previously accepted values into the newly created content.
mmulich
added a commit
that referenced
this issue
Dec 11, 2014
This will sync the license acceptance with publishing when a revision is created.
reedstrm
added a commit
that referenced
this issue
Dec 11, 2014
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The licensor acceptance is wiped out when trying to revise a published document/binder (aka content). This is the main issue at the moment. Furthermore, if the license changes, all the licensor acceptances should reset.
The greater issue is a bit hairy. It is possible to initialize a revision on already revised content and have that content set all role acceptances to true, even for outstanding or rejected acceptances.
This can be corrected by syncing with publishing during the creation of the revision.
The text was updated successfully, but these errors were encountered: