I'm currently an xoops cms user and am looking for an alternative.  DNN looks like an excellent choice, but I do have a few questions.


1. Does DNN have a Private Message system for users?

2. I would want to import my users into the new system.  XOOPS uses MD5 encryption for the passwords.  What does DNN use?

3.  Is there a photo gallery module that allows for users to have their own albums as well as public ones?

4. The modules I would need in DNN are:
    Calendar, Service Directory, Forum, News, Photo Gallery

Thanks for your help.

Hello,

Welcome to the forum.

1) have a look at www.ventrian.com, they have a private messages module
2) To be honest I'm not sure what the encryption is. I know that it uses unique machine keys for each installation which are then used to interpret the encrypted password. - Could be worth asking in the main dotnetnuke forum - let us know if you find the answer to that as I would be interested to learn more about that.
3) Have a look at the simple gallery at ventrian.com
4) Forum I use www.activemodules.com - For the rest a good place to look is www.snowcovered.com where you can search through all of the developers various modules, you should be able to find what you need.

Hope this helps, thanks,

Lee

Lee -
Thanks for the reply.  I have installed a few of the modules and believe the transition to DNN will be soon.

As for encryption, DotNetNuke can use MD5 to hash user passwords. I'm actually digging into that for a project.

I presume that you want to bring existing users over with their passwords. If you've got the details on how the hashing is done on your current system and the key, you might be able to install that in DotNetNuke.

I would suggest that you set up a test installation (an installation, not a portal), set the encryption type to MD5 in your web.config, and try copying the existing key to (I think) the validation key.

Then create a user on your test installation for which you know the password. After that is set up, look in the aspnet_membership (?) database table and see if the hashed password matches what you've got on the old system.