Well admittedly the site i am using rolesignup on does have a lot of custom code.. but i dont think any of it should be causing this.
all my devel is done with caching disabled so i never noticed until now... but i have 2 links on my site:
user/register/role/5
user/register/role/6
it looks like from the code the module simply grabs the role # and throws it in a session var and then redirects to user/register.. then a user/register hook inserts a role entry.. pretty simple...
but the issue i see is that since module redirects to user/register that page gets cached... so if someone first selects link for role 5 and then later selects link for role 6; even though role 6 is going to be used... the registration form that i get is the cached version which is for the wrong role (5).
not sure if there is some other way to use this module that everyone else is doing such that no one has come across this.. but seems as though it can't work with this bug.
to fix for my project i simply do a menu hook in a custom module i have that dumps that cache entry whenever user/register is hit.
maybe this is because people have the same registration form regardless of roles.. hmmm.. did i mention that i use registerprofile module to have different register forms for each role?
Peter Lindstrom
LiquidCMS - Content Management Solution Experts
Comments
Comment #1
cyberswat commentedPeter, are you still using this module with 4.7? I really have no desire whatsoever to backport it.
Comment #2
cyberswat commentedRemoved the session bits and rewrote the module for Drupal 5. It should work properly with or without caching. http://drupal.org/project/autoassignrole