Force VB5 to use legacy over blowfish

[eleetoburrito]

We're using VB5 as forum for our main site, our users single sign on to VB from the main site and therefore we don't really need the features for users to sign up and register on VB.

We have a ton of users and we've been using VB 3.6.8 for a while so the majority of the users are using the legacy password scheme and were added into VB's users table the same way.

With VB5, if we were to clone the functionality of auto adding the users after registration on the main site, it'd be creating the user with the blowfish scheme instead of the md5 legacy scheme and that creates more work and more logic to detect if they're legacy or blowfish and we'd have to have diff sets of code. We'd just like to stick with one for all.

How do I use the api to create a new user and use the legacy scheme instead of the blowfish scheme?

[Paul M]

As best I can tell, you should be able to set the priority in the pwschemes.xml file.

Atm, legacy is set to 1, and blowfish to 10 (higher means try and use this first).

So if you edit that file and set legacy to 2 and blowfish to 1, it should default to using legacy by preference.

You will probably have to run the upgrader after updating the XML, so it re-imports the pw schemes.

[eleetoburrito]

great, thanks!