A very useful module. A good candidate for Drupal 8? Thoughts?

Comments

ohnobinki’s picture

What do you mean by inclusion into D8? Becoming part of the official distribution? That would be cool, but I don't think that this module is mature enough to deserve that.

We definitely start maintaining a drupal-8.x version of this module soon.

EugenMayer’s picture

Well no way this module should go as-is into d8, neither the d6 nor the d7 version. As ohnobinki said, its just a ok contrib, but a horrible API in general.

We should be able to:
- lock any kind of content ( entity id / object type / id )
-- API to even lock forms of a specific ID
- Having locking-strategies implemented in OOP, being able to replace / redfine / refine them for objects / types

optional
- clever permission settings ( also lock-breaking delegation )
- if you can break a log, email the current locker

The must haves need a complete rewrite of this module. This module has grown historically and has been polished by ohobinki a lot ( thank you!! ), but for a core module, its just to bad in the "bare bones", or lets say architecture.

For a core module, this module must work much more general and esp. expose some useful API for developers.

jrabeemer’s picture

API content locking seems to be a long term goal. Code cleanup seems to be the immediate goal. Views has locking and core node locking and notifications seems to be the next logical step.

pandaski’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
Category: Feature request » Plan
Issue summary: View changes
pandaski’s picture

Version: 7.x-2.x-dev » 8.x-1.x-dev
dianacastillo’s picture

Hi, Who can tell me what progress is being made on making the dev 8 module?

EugenMayer’s picture

This module has been abandoned and will not be ported at all. saying this is just to let you guys move on creating other solutions and not wait for this to happen

chr.fritsch’s picture

Status: Active » Fixed

We now have a D8 branch with a first working release. Have fun!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.