Skip to content
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

Issue 2606858 - Porting content_lock module to Drupal 8 #1

Merged
merged 7 commits into from
Feb 13, 2017

Conversation

juanolalla
Copy link
Owner

Drupal.org issue: https://www.drupal.org/node/2606858, and also: https://www.drupal.org/node/2606856.

We are working through a big patch to the initial D8 commit, branch 8.x-1.x of this repository. Using this pull request to easily manage this big patch and adding issues to it, while we get it committed by the current maintainer.

juanolalla and others added 7 commits December 13, 2016 18:42
…_lock] Content locking (anti-concurrent editing)
2606858 - Issue #2 Add an "Unlock" button to cancel locking after editing
Implement custom access checker for every breack content lock form us…
Config changes required for the new Strict Schema testing that is ena…
@martincollar
Copy link

Thanks for you work! This should be merger already to module.. Btw one note, route content_lock_timeout.settings_form should require "administer content lock" permission instead of "access administration pages"

@juanolalla
Copy link
Owner Author

I think you're right @martincollar, I've created an issue for that #8

@juanolalla juanolalla merged commit 72bb506 into 8.x-1.x Feb 13, 2017
@juanolalla juanolalla deleted the 2606858 branch February 13, 2017 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants