Skip to content
Snippets Groups Projects
Select Git revision
  • 869a91b72eaf85a447e8fd1b78aad51a8b5676cc
  • 11.x default protected
  • 11.3.x protected
  • 11.2.x protected
  • 10.6.x protected
  • 10.4.x protected
  • 10.5.x protected
  • 11.1.x protected
  • 11.0.x protected
  • 10.3.x protected
  • 7.x protected
  • 10.2.x protected
  • 10.1.x protected
  • 9.5.x protected
  • 10.0.x protected
  • 9.4.x protected
  • 9.3.x protected
  • 9.2.x protected
  • 9.1.x protected
  • 8.9.x protected
  • 9.0.x protected
  • 10.4.9 protected
  • 10.5.6 protected
  • 11.2.8 protected
  • 11.1.9 protected
  • 11.2.7 protected
  • 11.3.0-alpha1 protected
  • 10.5.5 protected
  • 11.2.6 protected
  • 10.5.4 protected
  • 11.2.5 protected
  • 10.5.3 protected
  • 11.2.4 protected
  • 10.5.2 protected
  • 11.2.3 protected
  • 10.5.1 protected
  • 11.2.2 protected
  • 11.2.1 protected
  • 11.2.0 protected
  • 10.5.0 protected
  • 11.2.0-rc2 protected
41 results

drupal

  • Open with
  • Download source code
  • Dries Buytaert's avatar
    - Patch #11505 by Steven: 'my account' information is not saved.
    Dries Buytaert authored
      + Drupal 4.4 stored profile data in the serialized user->data column. Drupal 4.5 stores profile data in tables (but user->data is still available and used for other stuff, like locale or themes).  The update from 4.4 to 4.5 didn't remove the old data from the user->data column properly, because there is no mechanism in user_save to do so (it did try to unset the fields, but this has no effect).
    
      + On registration, hook_user('insert') is invoked after saving the data column. This means that any module-specific data is put into the data field. We cannot move hook_user('insert') higher up, because before that point, we do not have a complete $user object yet.
    869a91b7
    History