Skip to content

Non-superusers stuck on /preview/ after clicking "Edit" due to version lock (resolved by granting delete_versionlock permission) #461

Open
@phipier

Description

@phipier

Hi there,

After migrating to Django CMS 4.1.4, I ran into an issue where non-superuser editors were unable to access the edit mode of a page, even though they had the appropriate permissions via the updated migration script (djangocms-4-migration v0.2.0).

Here’s what happened:

Users would click the "Edit" button, but the URL would remain on .../preview/ instead of changing to .../edit/.

Manually changing the URL to /edit/ would redirect back to /preview/.

The plugin dropdown and text editing behavior (Text CKEditor) did not appear, and the text was not editable.

A new draft was created correctly, and the version lock appeared to be active (visible via the toolbar).

Everything worked fine for superusers.

What fixed it: Granting the delete_versionlock permission (djangocms_versioning | version lock | Can delete version lock) to the editor group resolved the issue. After this, editors were able to enter edit mode and interact with existing plugins as expected.

Expected behavior:

Editors should be able to access /edit/ for drafts they create (especially when DJANGOCMS_VERSIONING_LOCK_VERSIONS = False).

Version locking shouldn’t prevent users from editing their own drafts unless a permission is missing and the lock is active.

Environment:

Django CMS 4.1.4

djangocms-versioning 2.2.1

Migration via djangocms-4-migration v0.2.0

DJANGOCMS_VERSIONING_LOCK_VERSIONS = False

Let me know if I can provide more details or screenshots — happy to help!

Thanks a lot for the great work you’re doing on Django CMS 🙌

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions