Skip to content

FidelityInternational/djangocms-version-locking

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

FreemanFreeman
Freeman
and
Freeman
Aug 8, 2024
6e42193 · Aug 8, 2024

History

90 Commits
Aug 8, 2024
Aug 8, 2024
Aug 8, 2024
Aug 8, 2024
Mar 12, 2020
May 16, 2024
May 24, 2019
Oct 25, 2018
Feb 15, 2019
Sep 21, 2018
Jan 13, 2022
Aug 8, 2024
Aug 8, 2024
Aug 8, 2024

Repository files navigation

django CMS Version Locking

Explanation

The version-locking addon is intended to modify the way djangocms-versioning works in the following way:

  • The primary change is that it locks a version to its author when a draft is created.
  • The lock prevents editing of the file by anyone other than the author.
  • That version becomes automatically unlocked again once it is published.
  • Locks can be removed by a user with the correct permission
  • Unlocking an item sends a notification to the author to which it was locked.
  • Manually unlocking a version does not lock it to the unlocking user, nor does it change the author.
  • The Version admin view for each content-type registered with Version-locking will be edited to add in lock icons / buttons UI to the Actions column.

Installation

The package djangocms-versioning and djangocms-moderation need to be installed for this project to function correctly.

Configuration

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. See the cms_config.py file for an example of how. In this file the PageContent model is configured for version-locking.