Drupal Diary, January 2009
January 27, 2009
chrisyakimov
Just some housekeeping so I don’t lose track of what I need to do. If any of you are reading this, and you’re not me, please forgive me singularly ego-centric writing: this blog is primarily designed to be a notepad for me to keep myself in check. If any information here helps you out – awesome (and I’m happy to respond to questions/comments etc.).
Rad, here we go.
Importing Users has become rather complicated. I considered the User Import module, but it isn’t built for Drupal 6. Node import might work, but I had memory issues configuring it. It’s working now, but in the interm, I have mapped the database to database migration that needs to take place, and am executing SQL to make that happen.
User Profile Module is just… non-conformist! I wish there were some code out there integrating User Profile with CCK. I guess I could experiment with a Profile content type, but I wonder how to limit each user to only one… Wishlist content.
So:
My Current Isse: Sending old users a new drupal login string with a new temp password.
Options:
1. MD5(“temp”) for all of them – send list generated email with that info. Very insecure.
2. Employ Drupal’s “forgot password” functionality – provide instructions on the first page to log in to generate a temp password for themselves. This actually sounds like a fantastic option as I have all the emails and login information, and have managed to migrate that into the users database. But I gotta test it and my development environment is not setup to send mail. So I have to get this live.
REMINDER
Set one of the imported accounts to “active” once the migration has ocurred flawlessly. Test that account to see if a live installation will functionally send a temp password for the imported account and get everything running.
Entry Filed under: Uncategorized
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <pre> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to comments via RSS Feed