-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update README.rst #45
Conversation
Updated for RST
Tidied markup
README.rst
Outdated
Version-locking makes use of the django-cms 4.x App Registration mechanism to allow models from other addon's (i.e. content-types) to be registered for use with version-locking. | ||
`®` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
®?
README.rst
Outdated
|
||
- The primary change is that it locks a version to its author when a draft is created. | ||
- That version becomes automatically unlocked again once it is published. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure how a published version could be locked? I mean AFAIK a published version cannot be edited even without locking (if a draft version doesn't exist the edit button actually creates a new version).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well. Draft versions are locked. If we didn't remove the lock when publishing, then it would stay locked.
Clarifications
Updated for RST