Hi there,

Im new to mojoportal and im helping a website out to maintain and develop further. First thing i would like to do is to update the website to the latest version. One of the things that has been changed in the new version is the password hashing. This might be a big issue for us. The reason for that is that user dont only login via the website which means if we upgrade and they log in outside the website the password check will probably fail because our app uses different hashing.

What I would like to know is if running a script to rehash all the passwords in the database and then upgrade our hashing in our app would be a good idea when upgrading to the latest version. Any help with that is appreciated :-)

Thanks for any answer!

Hi Joe,

Thanks for the fast reply. It seems we can work around the hashing problem by editing our app. Basically we will do the same as the website, check if the password matches to old way if it does rehash it if it doesnt check if it matches with the new hash if not login invalid.

I do however have another question. I just noticed someone registered a assembly for a custom .dll in some of the master pages so that we can show some additional information on the profileview.aspx page(which is also edited). I assume that if we upgrade we will lose our customization to the master pages because we will override the files. Will it be enough to add these added lines in the new copied files?

Yea, that is the point it seems the mojoportal code has been modified. For example the $root/ProfileView.aspx and $root/App_MasterPages/layout.master.aspx has been modified to register the custom .dll.

There are no major changes so im guessing editing these files after copying the new deploy files will be enough. We'll see :-) 

Awesome, I'll change that when deploying the new version.

Hi Joe,

Do you have any idea what may cause this problem? I reproduced the problem by changing the setting in the demo portal to -1 and wasnt able to edit any of my own posts.