You are here

Home » API reference » LoginToboggan 6

UPGRADING.txt in LoginToboggan 6

Same filename and directory in other branches
  1. 7 UPGRADING.txt
*******************************************************
    UPGRADING.txt for logintoboggan.module for Drupal
*******************************************************

5.x to 6.x:

1. The 'Set password & Immediate login' functionality has been split out into
   separate 'Set password' and 'Immediate login' features.

2. The behavior of LoginToboggan's 'Redirect path on Confirmation' setting has
   changed in the case where users are NOT setting their own password on
   registration. The previous behavior was to automatically redirect the user
   to 'user/%uid/edit', with a final destination of the 'Redirect path on
   Confirmation' setting. This behavior has been removed. To replicate it, the
   path must be explicitly declared now. 
     Ex: to have the user visit their edit page, with a final destination of
         node/foo, you would use: user/%uid/edit?destination=node/foo

3. A new 'Delete unvalidated users after' feature has been added. This feature
   is handy for automatically cleaning up spam registrations.

File

UPGRADING.txt
View source 
  1. 

  2. *******************************************************

  3.     UPGRADING.txt for logintoboggan.module for Drupal

  4. *******************************************************

  5. 

  6. 5.x to 6.x:

  7. 

  8. 1. The 'Set password & Immediate login' functionality has been split out into

  9.    separate 'Set password' and 'Immediate login' features.

  10. 

  11. 2. The behavior of LoginToboggan's 'Redirect path on Confirmation' setting has

  12.    changed in the case where users are NOT setting their own password on

  13.    registration. The previous behavior was to automatically redirect the user

  14.    to 'user/%uid/edit', with a final destination of the 'Redirect path on

  15.    Confirmation' setting. This behavior has been removed. To replicate it, the

  16.    path must be explicitly declared now. 

  17.      Ex: to have the user visit their edit page, with a final destination of

  18.          node/foo, you would use: user/%uid/edit?destination=node/foo

  19. 

  20. 3. A new 'Delete unvalidated users after' feature has been added. This feature

  21.    is handy for automatically cleaning up spam registrations.