DNN_Platform_9.10.2

This is on a new install.  Other old sites same rev might have been updated work ok

Changes below don't solve it

<< 

• REGISTRATION SETTINGS

User Registration

• None
• Private
• Public
• Verified

Registration Form Type

• Standard
• Custom

Registration Fields:

Username×

Save error

Settings>Site Settings> Site Behavior> User Profile are only Visable  None Required

Are there any updates on this?  Two months have passed. I just installed the lasted DNN and I am having the same exact issue.

Set Registration Form Type to Custom.  Try to add any fields to Registration fields starting with UserName and it throws this error.

Could not update the registration settings. Please try later.

Error in JS console shows

I am having the same issue, on top of Verified registration not sending emails to verify and resend also not working. 

I checked an older DNN version and it works fine. V. 9.01.01 

So how does this work now with DNN?  You find a bug, post in the forums and it goes off into the ether to never be answered or dealt with?  What is the proper mechanism to report issues now?  Is there anyone that actually fixes these issues?

Haven't used DNN since 2012 but really rethinking my choice at this point.

The forum is for discussing things :-) And of course, to get help how things work.
Bugs and enhancement requests are logged on https://github.com/dnnsof.../Dnn.Platform/issues

That's where people can elaborate on bugs and post the code that will solve things. If you are not able to code, you will be depending on others who do. Meaning that your bug will be triaged and if it is a bug that many of us encounter, it will get more priority than bugs that happen in just a few usecases. If you are not a code and want to speed things up, you can always try to do it as I do (I am not a coder myself): make it a paid job. On top of my head, I know Daniel Valadas has a donation option for Github work. 

I did report this issue on the GitHub issues list.  If anyone wants to trackit, here is the link https://github.com/dnnsof...Platform/issues/5232

I would not hold your breath on it being fixed as there are issues open still from October of 2021 through now that have not been addressed.

Posted By Dave VanderWekke (AWE) on 19 Aug 2022 08:28 AM

I did report this issue on the GitHub issues list.  If anyone wants to trackit, here is the link https://github.com/dnnsof...Platform/issues/5232

I would not hold your breath on it being fixed as there are issues open still from October of 2021 through now that have not been addressed.

Hi Dave,

I feel the need to explain you a bit how this project (and any Open source project) works.
As DNN platform is now fully under the control by the community, this means that all development work is done by volunteers.
In general this means that issues being logged are fixed if one of these volunteers feels the needs to get it fixed, there's no process in place that makes sure all issues are fixed. Actually, issues that have been open for toolong get closed automatically.
Companies that don't have any in house developers can also sponsored a developer to get an issue fixed that's important to them. We have done so in several occasions (no, this is not meant as self promotion) but normally we also spend time on issues that are important to us or our clients.
So you are right, don't hold your breath, as, if no-one in the community feels the urge to fix an issue, it will most likely not get fixed.
 

Thank you for explaining how DNN Platform issues now work.  I've been a .NET dev for 20 years and a software dev for over 30 so I understand open source.  I also developed modules and contributed to DNN back in the early days.

We use a ton of open source nuget packages in our apps.  They however get the attention they need as there are usually a dedicated team of volunteers that work on fixing them. With DNN it seems like volunteers are willing to make enhancements that may create bugs but unwilling to fix those bugs they created.