[support] Migrating users from d5 to d7
Frans Kuipers
franskuipers at gmail.com
Mon May 31 09:43:50 UTC 2010
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/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20100531/78ced51c/attachment.html
More information about the support
mailing list