- 🇨🇦Canada bohemier Québec city, Qc
AFAIK, there are 2 key differences between this module and the core Workflows module:
1- Workflow access: Provides a way to control access to content according to their workflow state
2- Fieldable: This module allows a workflow state to be attached as a field to an entity. Though as mentioned by SocialNicheGuru, "Now there is the workflows_field module for core workflows (http://drupal.org/project/workflows_field)" I haven't tried that module. - 🇬🇧United Kingdom somersoft
+1 for being enable to add workflow to different entity types, especially if they are custom entity types.
- 🇬🇧United Kingdom griz
There should really be an explanation of this on the module's project page. On first reading it seems like this must be a legacy module from before Workflows and Content Moderation were part of core.
Even once it becomes apparent this isn't the case, it's not clear what the differences are. - 🇨🇦Canada bohemier Québec city, Qc
Agreed this should be explained on the project page.
As for merging the functionalities with core Workflows, this would be ideal but AFAICT the 2 modules are architecturally very different, so I am not sure if this is feasible... Personally, I prefer the way this one (Workflow) works, having a more generalized workflow per field & entity approach. It allows for greater flexibility and expandability.
What is the situation now? I am on D10.3 and using the core Workflows module but I am having difficulties with getting nod visibilities to correspond to workflow states. Is this Workflow module still maintained and will it work in D11?
- 🇳🇱Netherlands johnv
@JohnWT, indeed, the contrib Workflow module is still very much alive.
ATM, as a maintainer, I have no interest in making a comparison between core Workflows module and this contrib Workflow module.