I am using ASPDNSF ML/DNN and have been having lots of issues with my Registration page not saving ASPDNSF data for several months now. It would save the DNN data and create the account, but the ASPDNSF data would be blank. If I went back a second time, the data would save. This in turn would cause errors on my cart page since the I am over 13 checkbox would not be saved. Ultimately it turned out that the Registration page was a url like this

http://www.uncommongames.com/Home/ctl/Register.aspx?returnurl=%2fCustomer-Login.aspx

In the iFinity URL Master I had the setting to use all lower case on URLs. For some reason, the word Register in the URL above has to have a capital "R". With a lower case 'r' it bombs.

If anyone knows why this is the case and if it can be changed, please let me know.

Also, I am using a specific page called Customer Login for my Login page. This is set in Admin Site Settings / Advanced. I am also using the Redirect After Login and Redirect after Registration setting found under User / Profile Properties and they are working correctly. These settings allow me to direct my customer to specific pages where I can explain more about why I require a Registration and where to go after registration.

ASPDNSF Support was insisting that I could not use a custom Customer Login page and that the Redirects After Login and Registration were also causing issues. As mentioned above, the only issue was the lower case r in the word register in the URL. Again, it would be great to know why the lower case is required and if it can be changed somehow.

Hope this helps others who might struggle with this in the future..
 

I don't know if you know this or not, but when you click on the game images in the carousel on your home page you get a 404 error with UrlMaster apparently not being able to figure out the Url.

Thanks for chiming in Bruce. And there is no need for an apology. Bruce has provided unending support for his products in an environment (ASPDNSF ML/DNN) that is challenging at best... undocumented and difficult for sure. And the Google Checkout Patch that ML/DNN just issued me last week was a holdup on my site as well.

I have posted a ticket with ASPDNSF to locate and correct if needed any hard coded url comparisons. If anyone knows of a valid reason why they would approach it that way, please let me know. I don't want to always place the blame on ASPDNSF for everything that goes wrong on my site, but typically it does end up being an ML/DNN issue. My assumption is that this capitalization issue is on their code.

Of course I did have an issue where I was using the Testify Module inside of a Live Content popup and it was firing behind the scenes when someone would try to post a Registration form. I was pretty hard on ASPDNSF because I thought it was their issue and it turned out to my issue. I just got lucky one day and clicked on the Testify Add Comment link and saw validation errors on the form. That was the clue I needed to determine that the Testify form was acting on the Submit Registration button. And yes, I went back to ML/DNN and let them know it was my fault.

It's going to take a while but I really do think that ultimately ML/DNN will be a very solid platform for eCommerce on DNN. How many people remember back in the DNN 1 and 2 days when the Text/HTML module was a disaster when switching between the basic and advanced editors? We lived with that for quite a while before it got fixed. ML/DNN will take a while to mature just like DNN.

So now that it looks like I can turn my PPC back on, I am pretty happy.