Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The patch applied and the views.zip extracted to the module folder should provide several handlers and definitions to integrate with views.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | content_lock-views.patch | 404 bytes | brunodbo |
| views.zip | 2.42 KB | franz | |
| content_lock-views.patch | 383 bytes | franz |
Comments
Comment #1
eugenmayer commentedHi Franz,
just to get the idea, what do we need the views integratio for? Kind of "show all locked nodes?".
Thanks
Comment #2
franzYes... I'm working on a project where there should be an interface for managing several nodes still in the workflow (not published), and the nodes list must show which ones are locked or not, and who's editing each project.
Comment #3
franzIt's a project where there are many people editing nodes all at the same time...
Comment #4
franzBTW, I'll be doing a lot of testing in the next months, so if you feel like, you can give me CVS access to take this part on my responsability.
Comment #5
eugenmayer commentedHi Franz, i will have a look a the patches and we can talk about co-maintaining that feature just after it.
greetings
Eugen
Comment #6
khad commentedhi franz,
this is exactly what I would need, so I already tried your patch. Gave me a "Parse error: syntax error, unexpected ')' in /var/www/drupal/sites/all/modules/content_lock/content_lock.module on line 606" initially, so I removed the mismatching ')', but then I could not see anything exposed to views - are your additions meant to do something visible already, or are they preparations for a views integration still to come?
Comment #7
franzYes, the patch has a mismatched parenthesis, sorry.
Anyway, removing it and clearing the caches should be enough for some new handlers to be exposed on views UI. Did you properly unzipped the views folder inside the module folder?
Comment #8
khad commentedSorry, just my stupidity - I didn't realize that I had to clear the cache to see it.
Seems to work flawlessly now, thanks a lot!
I just couldn't figure out how to show who is locking a node, is this already possible?
Just a cosmetic wish: I would prefer the 'is locked' field to display like a node's 'has new content' field - just the word 'locked' in red, or nothing at all. Can this be achieved somehow? (tried to do this with 'rewrite output', but couldn't get the desired result...)
Comment #9
khad commentedSorry again, I should have read through the code before posting the above - obviously, the lock owner is a relation.
This also allows for my intended display, great!
Could already have gone into stable, as far as I'm concerned...
Comment #10
eugenmayer commentedPlease set it to reviewed when you tested it.
I will happily include this into the next release then
Comment #11
franzkhad, I believe you can do this by theming the output of the field. Not sure exactly how as I haven't done it myself.
Comment #12
brunodboApplied & tested this patch today. Works great.
Attached is an updated version of the patch:
- Removed mismatched parenthesis.
- Minor code style fixes (missing space, new line above function comment)
Comment #13
franzI thinks this is ready then...
Comment #14
eugenmayer commentedGood job, thank you. did not find the time to include this yet, i will do so for the next release
Comment #15
eugenmayer commentedSorry for the huge delay, really was busy with the other modules. Implemented / included in 1.1.
Thank you very much for the contribution
Comment #16
eugenmayer commentedComment #17
eugenmayer commentedreleased in 6.2.0 rather then in 1.1. 1.0 will be discontinued
Comment #18
franzSorry for reopening, but maybe there is a need to document this.
Also, there could be a topic on the project page. =)
Comment #19
franzops, fixing component
Comment #20
eugenmayer commentedHey, good idea. As iam not familiar with the implementation, are you willing to write down some lines i include in the docs? We could also start a book page now, as the docs have reached a critical limit :)
Thank you for your effort, really appritiated.
Comment #21
eugenmayer commentedDone :)
Comment #22
franzSorry, kept postponing this for too long... =/