https://gitlab.synchro.net/main/sbbs/-/commit/5da1b1a2f3ed8654785558b2
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Use select_editor() and select_shell() - no functional change

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/6582c8d160ec255d0d5b6f78
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Check new user alias is non-blank and error-out if blank

Log warnings when using alias for blank user real name or handle fields

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/4182066dd508117f7cb04808
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Do user alias, name, handle validity checking - always

Don't depend on the newuser_prompt module to do this correctly (e.g. set the 'O' restriction here, detect duplicates, disallowed names, etc.).

The rlogin_name can always be used to initialize the useron.alias

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/7d85b0c7fb41b718b4dd7425
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Remove the new user prompts that are now handled in newuser_prompts.js

Since the newuser prompts mod defaults to this script name (if blank), there was really no way to revert to the hard-coded logic any more anyway.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/efba67a60bf19798272788c1
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Set SS_NEWUSER here, if it's important, it should be set in the C++ code

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/04542250c903f03d365c2da5
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Paranoia around new user strings ending in white-space

We can't be sure that a newuser_prompts mod will do the right thing

One confirmed bug was when a handle was not prompted for, the default handle (copied from the alias and truncated to 8 chars) could end in whitespace.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/ee5b3b1e6a49bb9311fd8852
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Change wording of new user registration complete/success log message

"New user registration completed"

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/3531759148c1dbbec0878f92
Modified Files:
src/sbbs3/newuser.cpp
Log Message:
Don't enforce unique real name or handle here if sysop opted not to prompt

the new user for those strings.

Eliminate the situation that Keyop reported in IRC whereby he had SCFG->System->New User Prompts->Chat Handle / Call Sign set to "No", but had Force Unique Handle / Call set to "Yes", resulting in a new user registration failure with error:
!ERROR in newuser.cpp line 138 (newuser) checking "New user handle ...

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net