Re: [development] No last access?
This does not seem to be a problem in 4.7.4 but in 4.7.5+ and 5.1 calling user_load() functions $user->access and $user->login give the updated values and not the actual value in the database. Carl Mc Dade ____________________________ Web Developer ----- Original Message ---- From: Carl Mc Dade <carl_mcdade@yahoo.com> To: development@drupal.org Sent: Sunday, February 11, 2007 9:43:37 AM Subject: [development] No last access? Is there no longer a last access functionality? using the global user and calling $user->access gives the value after the database has been updated. Not the value in the database at the time of login. Ex. the value in the database table is 0000002. You will not get this value but the value 0000003 which is the time of the latest access. Carl Mc Dade ____________________________ Web Developer It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265
Op zondag 11 februari 2007 10:36, schreef Carl Mc Dade:
This does not seem to be a problem in 4.7.4 but in 4.7.5+ and 5.1 calling user_load() functions $user->access and $user->login give the updated values and not the actual value in the database.
There were some security related changes made to the user _insert and _update. Maybe thye have to do with this? I suggest you browse through the cvs logs of user module to isolate the cahnges that cause this behaviour. Once identified, and detailed, I am sure there are people willing to help you solve the issue. It hmight have been an intentional change, it might have been a new bug introduced by one of the security fixes. Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl
participants (2)
-
Bèr Kessels -
Carl Mc Dade