The workflow access module grants permission based on states. In combination with the revisioning module the state of the node might change while the published revision remains as is and should be visible. This patch adds a checkbox "Allow users to always view published content (especially useful with the revisioning module)." to the workflow access form which bypasses state based permission checks for viewing published nodes. That solves all the many many requests, bug reports, complaints whatsoever around here about using workflow with revisioning.
I'm not aware of any side effects, however, I'd be glad if someone could have a look at it so we don't open holes here.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | allow_viewing_published_content_with_records2.patch | 4.07 KB | Tim-Erwin |
| #1 | allow_viewing_published_content_with_records.patch | 3.99 KB | Tim-Erwin |
| allow_viewing_published_content.patch | 3.1 KB | Tim-Erwin |
Comments
Comment #1
Tim-Erwin commentedWell, with hindsight I thought, maybe hook_node_access() is not the best pick, as it is not respected by views (correct?) etc. Attached you find a patch that does not look as clean, but solves the issue using the node_access table. It adds records with view permissions for anonymous and authenticated user if they don't yet have one.
Comment #2
Tim-Erwin commentedUps, I forgot to limit the access to published nodes. Fixed it.
Comment #3
nancydruGiven the limited audience could this be done as an add-on module?
Comment #4
johnvThis might be possible if Workflow were a 'true' Field API field, as proposed in #2019345: Create a 'Workflow Field' with Widget, Formatter, Fieldtype
Comment #5
johnvLet's focus on #2019345.
Comment #6
johnvThis should be working now using Workflow Field, which contains support for Node revisions. Please re-open if there is a problem.