Hi,

2.3.6.7 has not been released yet so you must be working from the source code repository.

Thanks for the bug report, this must have been introduced by some recent work I did in the registration page to get rid of the default table rendering of the CreateUserWizard. I must have removed the wiring of some events as a test and forgot to put it back afterwards.

I just fixed this and pushed it to the repository so if you get the latest changes and rebuild it should be fixed.

Best,

Joe

Well, ultimately you'll need to make that decision yourself. I will say that generally I try to keep the default branch in the repository stable and I don't make mistakes that often but I am human and this was one of those few occasions.

From my end the more people who work directly from the repository the better because that helps me if bugs are found before they make it into official releases. And as you just saw, if a bug is reported and you are working from the repository it will get fixed very quickly. So, working from the repository means you get bug fixes and new features much sooner than if you use release packages. If a bug does make it into an official release it depends on the severity of the bug, for this particular bug if it had been reported after making the next release I would have felt it needed an immediate fix since so I would have put out an update within 24 hours. Whereas for lesser issues one might have to wait for the next release to get the fix if not working from the repository. We typically ship a release about once per month so it is never a long time between releases. But it can be very nice to have a fix within minutes or hours.

I'm always running newer builds on this site and the demo site to try and catch any problems before they make it into a release but having others who also do this is a big help to the project. If someone has a big mission critical site the onus is on them to have a testing environment and their own QA team no matter whether they work from the repository or from official releases but if they find a problem it is actually easier to help them faster if they are working from the repository. We don't have a dedicated QA team, so we rely on the community and our own testing on our own sites but we try to respond quickly on those few occasions where a problem does emerge (no matter whether in the repository or in a release) and it is easier to respond quickly for the folks who do work against the repository.

I suppose the safest approach for those who have a mission critical site and don't have the capacity to do much testing is to use official releases but wait a week after the release before upgrading to see if any major bug reports come in from the early adopters who upgrade right away. But in all cases we don't intend to leave anyone hanging with a major problem for long if it is reported with steps to reproduce it, we'll fix it quickly and if needed ship an update.

Best,

Joe

This is a system required field on the profile page it is not optional. For this specific feature the profile config file only determines if it is shown on the registration page so the user can choose it right away as part of the registration process.

If the default is left blank then it defaults to the time zone from site settings. If you set a default value it must be a valid time zone id or it will be ignored, you would have to view the source of the page that has the time zone list to see the valid values.

The help links should work with custom settings but this one isn't really the same as the custom settings and isn't loaded the same way because it is a system required field.

Hope that helps,

Joe

your setting as posted is malformed

you need to move the angle bracket from after includeHelpFile to after defaultValue

Hope that helps,

Joe