I migrated a whole lot of content from bbPress over to my discourse installation. I can see all posts and users and stuff. But my users can’t login using their “old” password data from my WP site. I installed the plugin, its listed in my plugin section of my admin area. I checked all the available check marks.
Still: nobody can login!
I also have no idea where to apply the given code from the plugin’s readme:
user = User.find_by(username: 'user')
user.custom_fields['import_pass'] = '5f4dcc3b5aa765d61d8327deb882cf99'
user.save
Also I have no idea what exactly is meant by alternative password hashes talked about in the readme.
@michaeld could you provide some more guidance on how to use the plugin?
Oh my god, after some more testing it turned out that it actually worked. The problem was a changed password when I tested it Sorry! Thanks for the great plugin! Made my life a lot easier!
Hi, I’m having problems making this work. I’ve created a custom field import_pass and installed the plugin. Ran the import script once again on my SMF database but with no luck, no one can login afterwards. On the custom field I can see just a “-“ instead of some hash.
Like other users pointed out before, not sure what do with this:
user = User.find_by(username: 'user')
user.custom_fields['import_pass'] = '5f4dcc3b5aa765d61d8327deb882cf99'
user.save
Appreciate any guidance Does this code go in the smf2.rb import script file or what?
That won’t work. But there is no need to install the plugin during import, or to create a custom field manually. It should be handled by the SMF2 script already. So something else is up.
The code is there as an example for script authors. It’s already in the SMF2 script.
Thanks. That’s great. So you mean, if I remove the manually created custom field and just keep the plugin activated, then it should work by itself and pick up the password hashes when it needs too.
Is there a log we can check to see why the plugin isn’t doing what is supposed to?
The plugin takes care of interpreting and using the custom fields that have been set by the importer. If the custom fields are empty or not there, then it is not an issue with the plugin, but an issue with the importer.
You should install the plugin on the instance that is actually running the migrated forum.
We have seen instances where the plugin caused issues when it was installed on an instance that was actually running the migration script, so we recommend against installing it there.