The rejection is not the last word. This is just something core maintainers do from time to time: somebody reports a problem, and a maintainer who hasn't run into the problem tries to claim it's part of Drupal's design. Usually the maintainer succeeds in preserving the bug for only one release cycle. Unfortunately, that very likely means we will have to live with this problem until Drupal 7. On Aug 27, 2007, at 11:45 PM, Ron Parker wrote:

OK, I understand that Drupal doesn't support changing user roles on the fly. Technically, OG User Roles does not change any sitewide roles; it only adds roles based upon the group that an individual node belongs to. But, I won't quibble with details.

What I don't understand is why my request to add the ability to reset the user_access() permissions cache was rejected. http:// drupal.org/node/170524

The requested code addition does not alter existing permissions in any way. It simply provides a method whereby one can send a command to user_access() to reset the static variable. Can someone tell me why this is not a reasonable thing to be able to do?

Thanks!

...

...

The permissions (user roles) are being altered temporarily. The reasons are documented in the issue Ron has referenced.

I've said it once and I say it again since apparently nobody noticed:

Temporarily changing user roles (per page request) is (currently) unsupported by Drupal.

I'd even argue that it shouldn't be supported and that what Ron is doing should be achieved in another way.