Revisit the decision to enforce the CMS new user account option, allow CiviCRM to create CMS user accounts when CMS has public registrations disabled
Raising this a request to revisit the decision originating in 2009 (CRM-4036) to enforce the CMS new user account option and instead allow CiviCRM to create CMS user accounts when CMS has public registrations disabled.
There are three key reasons to have this functionality:
- Public registrations on websites attract spamming and therefore require moderation and anti-spam systems to be in place.
- For member-only websites, the method to because a member is using the membership sign-up form (CiviCRM) and when the membership fee is paid, that's when the corresponding CMS user account should be created. And not by any other means.
- With user account creation disabled, a separate and in some cases manual process needs to be performed to create the corresponding user account for members - which is a waste of effort.
With the current logic where CiviCRM uses the CMS configuration, the site must be open for public user registrations to support CiviCRM registering a member user account.
The change is relatively simple and would be removing the check of the user registration option for each supported CMS. Thus CiviCRM Profiles can be used to create CMS accounts.
See also related, User Profiles, the User account registration option is displayed even when the CMS has the "User can register" option disabled - user-interface#41 (closed)
Agileware Ref: CIVICRM-1809