We recently were required to move our DNN (v4.9.5) site to a new server. We moved everything, including the DNN files and the databases to which it is connected. Everything works fine except when the users click "register". The UCanUse.UserAttributes module shows up, but is missing all the information fields, such as first name, last name, email address, etc. We've tried removing and re-adding the module again, but nothing shows up. On the server where we copied the data, everything appears normally. Comparing the settings between the two, they are identical. The UCanUser .dll's are all present. Do we have to register or install something?

If you are absolutely certain that your database and web directory is identical to the old server, then the only variable left is the old server.

Are you using the same versions of ASP.NET, SQL Server, and is the website configured the same? Is the AppPool using the same Managed Pipeline Mode?

Everything appears to be configured the same.

Does anyone know if UCanUse is still supported? I tried emailing to an address I found in some other forums (support@ucanuse.com) but it appears to be bouncing around in cyberspace. I'm doubtful it will find its destination. The website UCanUse.com doesn't seem to exist anymore either.

I think that UcanUse is gone.

Do you have complete source code for the module?

And is DNN still 4.9.5?

Yes, I think you're right. UCanUse is officially gone. But I was able to track down the "owner" through other old posts from a forum on the DNNsoftware site and Googling his name, which led me to an email address to contact. He's been kind enought to look at our issue now and we think we've identified the problem.

It turned out to simply be that under Site Settings/Security, registration was not set. That is, none of the radio buttons were selected. In the database the value was set to -1. According to some UCanUse.User Attributes documentation we were finally able to access, that value must be set for the fields to display. We selected the private registration option, and the missing fields now displayed.

Strangely, on the original site it is exactly the same, but there was a second portal set to public registration. Just guessing, but we think because the module was being shared between the two portals, the "public" setting on the second portal was allowing the fields to display. On our new server that second portal was disabled, so the setting on the active portal was now the only thing telling UCanUse whether it should display those fields.

Excellent!

And kudos to Mr. UCanUse for stepping up and helping you our!