In the Auto Logout Roles configuration I have disabled the roles "authenticated user" and "administrator", while all other roles are enabled. Although I am member of the "administrator" role I will still be auto logged out. So there seems no way to disable autologout for certain roles.

Comments

roball’s picture

roball commented

Had to entirely disable this module for now since this bug is really annoying - sorry.

levelos’s picture

levelos commented
Status: Active » Closed (cannot reproduce)

I tested a similar situation and can't recreate, and no one else has reported a similar issue or concurred with this one (about 120 registered users of this branch). Keep in mind that any registered user is automatically in the authenticated role. If you add a user to, say myrole, then they are in at least 2 roles, authenticated and myrole.

smptebars1’s picture

smptebars1 commented
Status: Closed (cannot reproduce) » Active

I have the same issue. I have the timeout set at 15min. I have editor and admin excluded. Altho it does not exclude them..... they time out just like all the rest

roball’s picture

roball commented

Good to know there are now other users experiencing the same problem with 4.0. This is the reason I am still using 6.x-2.4 (unfortunately, 2.5 is too buggy as well).

jack.r.abbit’s picture

jack.r.abbit commented

I think this ticket is the same thing. I posted a explanation and solution.
http://drupal.org/node/1131060

skizzo’s picture

skizzo commented
Status: Active » Closed (duplicate)

closing (duplicate)

roball’s picture

roball commented
Status: Closed (duplicate) » Active

Not exactly a duplicate. The other ticket suggests to re-implement the logic.

jack.r.abbit’s picture

jack.r.abbit commented

Well... they are the same thing... you just list a specific deselected role (administrator) while the other is more general to any deselected role. I would argue that both issues are a result of the same flawed logic being used to determine if a role should be logged out. I feel the fix for either one (and actually there is a third ticket reporting the same issue: http://drupal.org/node/1043918) is to reverse the logic as I did. With the current logic, this issue will never be fixed unless more logic is put in place to specifically exclude the "administrator" role. But why do that when you can just fix how the general logic is implemented and make it so you truly can exclude any role?

This ticket may have been the first of those three reported but the one I posted the fix on seemed to be the most general explanation of the issue. But I don't generally go and close other people's tickets for projects I'm not part of. I just posted the code that fixed my site. If the module creator notices and makes the change, cool. Otherwise, what ever.

roball’s picture

roball commented

Thank you jack.r.abbit for your code at #1131060: Role enforced despite not being selected.. I agree this issue, the other one and #1043918: Provide Should/Should-Not configuration logic can be solved by re-implementing the logic you suggested. Since this ticket is the one that has been opened first the other ones should be treated as duplicate. Also, only in this issue the module maintainer (levelos) gave feedback, although saying "can't recreate, and no one else has reported a similar". Now, where several users reported this problem over 3 tickets, I hope the maintainer changes his mind and accepts this to be a problem.

jack.r.abbit, could you please post your suggested solution as a patch attached to this issue?

johnennew’s picture

johnennew commented
Version: 6.x-4.0 » 6.x-4.x-dev
Status: Active » Closed (duplicate)

This issue is an old one! I think the problem as described does happen on the 4.0 release due to a number of issues which have all now been addressed.

The latest 7.x-4.x branch fixes this and 6.x-4.x will be fixed when the following backport is implemented:
http://drupal.org/node/1700706

Despite this threads venerable age, I am marking as a duplicate since the other issue has the patch on it.