I have a site running drupal 5. The next version of the site will be using drupal 7. The content is going to be all new, but I will need to migrate the existing user accounts and passwords. Is there an easy way to do that?
Could migrate data faster with TW than how Drupal.org suggests: http://www.lullabot.com/articles/drupal-data-imports-migrate-and-table-wizar.... I'm no expert, and maybe this will encourage a better reply. I've only worked with Drupal 6, and soon 7.
# Minor and major releases have different upgrade procedures - http://drupal.org/upgrade "If upgrading from one major version to another, such as from 4.6 to 6.16, you must upgrade to the latest release within your site's major version (4.7), then the latest release within the next major version (5.22), and finally to the latest release within the current major version."
On May 29, 2010, at 15:10 PM, Roy Smith wrote:
I have a site running drupal 5. The next version of the site will be using drupal 7. The content is going to be all new, but I will need to migrate the existing user accounts and passwords. Is there an easy way to do that?
-- [ Drupal support list | http://lists.drupal.org/ ]
The main problem if you export and import only the users will be the passwords I think. Drupal 7 uses a new password hashing algorithm (see http://drupal.org/node/29706), so you cannot just copy the user table. Probably best would be to make a new fresh Drupal 5 installation with only core and garland as theme, copy the user table in there (f.i. with phpmyadmin or backup_migrate module) and then perform the consequent updates of that simple installation to d6 and d7. When you run update.php to finalise the d7 installation the passwords will be updated.
Hans www.koba.be
2010/5/30 Kevin Davison kevin@quevin.com
Could migrate data faster with TW than how Drupal.org suggests: http://www.lullabot.com/articles/drupal-data-imports-migrate-and-table-wizar.... I'm no expert, and maybe this will encourage a better reply. I've only worked with Drupal 6, and soon 7.
# Minor and major releases have different upgrade procedures - http://drupal.org/upgrade "If upgrading from one major version to another, such as from 4.6 to 6.16, you must upgrade to the latest release within your site's major version (4.7), then the latest release within the next major version (5.22), and finally to the latest release within the current major version."
On May 29, 2010, at 15:10 PM, Roy Smith wrote:
I have a site running drupal 5. The next version of the site will be
using drupal 7. The content is going to be all new, but I will need to migrate the existing user accounts and passwords. Is there an easy way to do that?
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
On May 30, 2010, at 5:18 AM, KOBA | Hans Rossel wrote:
The main problem if you export and import only the users will be the passwords I think. Drupal 7 uses a new password hashing algorithm (see http://drupal.org/node/29706), so you cannot just copy the user table. Probably best would be to make a new fresh Drupal 5 installation with only core and garland as theme, copy the user table in there (f.i. with phpmyadmin or backup_migrate module) and then perform the consequent updates of that simple installation to d6 and d7. When you run update.php to finalise the d7 installation the passwords will be updated.
OK, that sounds workable, for a one-time procedure.
Is it really necessary to do the intermediate d6 install? Do all of d5, d6, and d7 have mutually incompatible user tables, so I need to wash the data through both upgrade conversions? If I did a clean d6 install, could I just drop my d5 user table into that database, then do the d6-d7 upgrade?
Actually, this is the tip of a larger question about user administration. What I really want is to have all account management centralized. This is a club website which has a public section (visible to anonymous) and a members-only section, which is only visible to authenticated users. As people join and leave the club, I'd like to have some automated way to push add/change/delete updates to the site user list. Are there tools to do this?
In theory, authenticating against some external authority (LDAP, kerberos, etc) would be good, but we're not big enough to have that kind of infrastructure. Pushing updates would be good enough for our purposes.
BTW, putting on my security hat for a moment, I agree with the move away from unsalted MD5. It's just not a viable technology any more for applications where it security matters.
On May 30, 2010, at 5:18 AM, KOBA | Hans Rossel wrote:
The main problem if you export and import only the users will be the passwords I think. Drupal 7 uses a new password hashing algorithm (see http://drupal.org/node/29706), so you cannot just copy the user table. Probably best would be to make a new fresh Drupal 5 installation with only core and garland as theme, copy the user table in there (f.i. with phpmyadmin or backup_migrate module) and then perform the consequent updates of that simple installation to d6 and d7. When you run update.php to finalise the d7 installation the passwords will be updated.
OK, that sounds workable, for a one-time procedure.
Is it really necessary to do the intermediate d6 install? Do all of d5, d6, and d7 have mutually incompatible user tables, so I need to wash the data through both upgrade conversions? If I did a clean d6 install, could I just drop my d5 user table into that database, then do the d6-d7 upgrade?
Think so. Even if user tables are not changed between D5 & D6, the upgrade D6-D7 expects ALL tables in D6 format.
Actually, this is the tip of a larger question about user administration. What I really want is to have all account management centralized. This is a club website which has a public section (visible to anonymous) and a members-only section, which is only visible to authenticated users. As people join and leave the club, I'd like to have some automated way to push add/change/delete updates to the site user list. Are there tools to do this?
Have a look at VBO http://drupal.org/project/views_bulk_operations (good way to test if D7 version is working as expected :-)
In theory, authenticating against some external authority (LDAP, kerberos, etc) would be good, but we're not big enough to have that kind of infrastructure. Pushing updates would be good enough for our purposes.
BTW, putting on my security hat for a moment, I agree with the move away from unsalted MD5. It's just not a viable technology any more for applications where it security matters.
-- [ Drupal support list | http://lists.drupal.org/ ]
-
Frans Kuipers -
Kevin Davison -
KOBA | Hans Rossel -
Roy Smith