Anonymous user displaying edit-page:

- doesn't lock / display 'is now locked..'
- doesn't print error message if it's already locked by an registered user until submitting (but i guess it's drupals default 'content locking' which is invoked then~)

Comments

bashFish’s picture

bashFish commented

- if anonymous user submit's, following fatal error appears:
Fatal error: Call to undefined function content_lockt_node() in /var/www/drupal/sites/all/modules/content_lock/content_lock.module on line 118

[even if the role anonymous user is selected under permission]

eugenmayer’s picture

eugenmayer commented
Status: Needs work » Fixed

Well for the first, anon-locking is not supported at all.

for that other issue, its solved already but not yet released. (typo in mehtod call).
So the typo is fixed in RC4

bashFish’s picture

bashFish commented

well the other issue is a part of anon-handling :S

why is it not supported? i'm trying to work on a patch~

greets

eugenmayer’s picture

eugenmayer commented

if you create a patch, make a submodule, i dont think i will include it in the core module. For anons, you need a complete different "handling", because a leaving anon is _gone forever_. You can never identify him/her again, so later unlocking cant be manually done by "you still lock a node". So thats were you will need that time-scheduled unlocking, but that one is going to be removed from content_lock core.

so actually, for anons and authenticated users the strategies are very different and the main goal of this module is to have a very strict strategy, which is only properly possible with authed users.

So rather create a submodule or a new module to go for that new strategy of locking / unlocking

Thanks for the feedback!

eugenmayer’s picture

eugenmayer commented
Status: Fixed » Closed (fixed)