Hope it's clear what I've writen. I suspect that uid1 is in all roles automatically. But that shouldn't be so for workflow module.

Comments

jvandyk’s picture

jvandyk commented
Status: Active » Closed (works as designed)

Inside Drupal, uid 1 has all privileges. See the notes in the Best Practices Guidelines regarding uid 1.

ultraBoy’s picture

ultraBoy commented
Status: Closed (works as designed) » Active

Useful info, thanx. But this isn't stated as requirement, but just as "Best practices guidelines". Note, that even in installation it wasn't mentioned that first account can be used only for administration tasks! It's just an advice currently. Therefore, untill this won't change, this should be considered as a bug.

I haven't seen the code, but maybe it's possible to fix this behavior in this module.

ultraBoy’s picture

ultraBoy commented

After all, Dries uses his account, right? Any problems about that? Do you want him geting bugs with this module?

jvandyk’s picture

jvandyk commented
Status: Active » Closed (works as designed)

uid 1 has all privileges in Drupal, including all workflow privileges.

ultraBoy’s picture

ultraBoy commented
Status: Closed (works as designed) » Active

1. The module works not correctly for uid1.
2. There are no reasons for that. (from user's, not coder's point of view.)

Therefore this needs to be fixed OR users need to be warned! (If you're still not agree, we should post about this to the developers list)

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Closed (works as designed)

please don't override the status assigned by the maintainer without a good reason. you are free to disagree and are free to encourage others to post arguments that support your position. you could even write a patch or hire someone to do so. post it here in case anyone else wants the functionality your describe. or at least write the warning which you *demand* gets added to the module.

it is a bit arrogant to switch status and demand the development email list care about this issue.

ultraBoy’s picture

ultraBoy commented

To jvandyk:

The issue is not my demand to fix this for me *personally*. My current customer can live with such behaviour of the module. I care about the module, because there is no doubt it has great possibilities. I got unexpected behaviour, but I wanted to prevent future users from getting this experience. This was the reason why I created this issue. This is my contribution.

That wasn't nice to play with status field, sorry about that. (Also, sorry that I didn't notice that you are the mainteiner!) But I wanted to pay others' attention because ... I find it very confusing. I repeat: currently there are no prohibition for using uid1 account. I understand the difficulty of implementation the correct behaviour for uid1.

But please understand users also. Bug "by design" is still a *bug*. Warn them at least. Well, seems like you want other people to repeat you my words. That's no problem, no hurry. (Again, sorry, I always do everything *too* active. I should have had more patience.)