Hello

I have classic user scheme in all of my projects:
root user (uid==1)
admin user (uid>1)
general user (uid>1)

Sometimes while I logged in root or admin I'm answering coments or posting the nodes without switching to general user just because I forget to :)
And if the authoring information itself can be easily changed later, some other things as content notifications to subscribers, etc. is releasing from the name of root or admin.

To avoid such things, I've made additional functionality to your great module to allow act admin roles as test users while posting nodes or comments.

Please, review this patch. I'll be happy if it will be commited.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

neochief’s picture

Status: Needs work » Needs review
FileSize
2.89 KB
1.36 KB

Oh, here it is

deekayen’s picture

Status: Needs review » Needs work

Instead of a checkbox, what about another submit button? I assume you're also aware that as content admin you're able to change the author textfield during the original writing as a way of pretending to be a different user...

neochief’s picture

Status: Needs review » Needs work

Yeap, I can do this too, but I can't really imagine situation in which root user needs to make content his own. And even if it's not a problem, why he needs to enable "Post on behalf" at all? From those perspectives, I thought that there is no need to write complicated logic (additional submit functions that doubles drupal's ones) for this functionality. Also, in my humble oppinion, additional submit button will make the form little uglier than it is :)

deekayen’s picture

I mean, can't you nodeapi on a submit button value instead of a checkbox value?

deekayen’s picture

Status: Needs work » Closed (won't fix)

I think you'll find there are more sensible ways to do this than adding it to masquerade - like just modifying the author during node creation.