CMS Made Simple Forums

The system works great and send emails to the user when registering, validating and being accepted to the FEU Module

The admin email seems to not be following the desired workflow, i.e.

User registers > email is sent to the user to verify > user verifies

at this point i would expect admin to get an email informing them that someone has registered

then I would expect the admin user would review the user and provide the new user with the ability to login to the private area

however, the "New Registration" email is only sent to admin once the admin has pushed the registered user to the FEU Users table from SelfReg Users table.

is there any way to change the process to send an email to admin once the User has verified that their email details? so that the admin can confirm the validity of the new user before the user can access to the private area?


CMSMS Version 2.2.10

Installed Modules
AdminSearch 1.0.4
CGCalendar 2.2
CGExtensions 1.62.1
CGSimpleSmarty 2.2.1
CMSContentManager 1.1.7
CMSMailer 6.2.14
Captcha 1.0
CmsJobManager 0.1.3
DesignManager 1.1.6
FileManager 1.6.8
FilePicker 1.0.4
FormBuilder 0.8.1.6
FrontEndUsers 2.13
MenuManager 1.50.3
MicroTiny 2.2.4
ModuleManager 2.1.6
Navigator 1.0.9
News 2.51.5
Search 1.51.6
SelfRegistration 1.14.3
TinyMCE 3.1.4

CMS Made Simple Config Settings
php_memory_limit
max_upload_size 128000000
url_rewriting mod_rewrite
page_extension
query_var page
auto_alias_content true
locale
set_names true
timezone America/New_York
permissive_smarty false
debug false
root_url http://www.codegroup.org
ssl_url https://www.codegroup.org
root_path Success /home/codegroup/public_html (0750)
uploads_path Success /home/codegroup/public_html/uploads (0755)
uploads_url http://www.codegroup.org/uploads
image_uploads_path Success /home/codegroup/public_html/uploads/images (0755)
image_uploads_url http://www.codegroup.org/uploads/images
ssl_uploads_url https://www.codegroup.org/uploads

Performance and Tuning Information (recommended settings, but not required)
Allow Browser to Cache Pages Caution Off (False)
Allowing browsers to cache pages will improve performance by not requiring your system to serve the page on repeated visits to a page.
Browser Cache Expiry Period (minutes) Success 60
PHP 5.5+ Opcode Cache Success On (True)
Enable Smarty Caching Caution Off (False)
Enabling Smarty caching can have serious performance benefits for most websites.
Do a Compilation Check Success Off (False)
Remove cache files that are older than the specified number of days Success On (True)

PHP Information
Current PHP Version (phpversion) Success 7.2.16
md5 function (md5_function) Success On (True)
JSON functions (json_function) Success On (True)
GD version (gd_version) Success 2
tempnam function (tempnam_function) Success On (True)
Magic quotes in runtime (magic_quotes_runtime) Success Off (False)
Is E_ALL enabled in error_reporting (E_ALL) Success
Is E_STRICT disabled in error_reporting (E_STRICT) Success
Is E_DEPRECATED disabled in error_reporting (E_DEPRECATED) Caution E_DEPRECATED is enabled
Testing for time difference in the file system (test_file_timedifference) Success No time difference found
Testing for time difference in the database (test_db_timedifference) Success No time difference found
Checking if the HTTPD process can create a file inside of a directory it created (create_dir_and_file) Success 1
PHP Effective Memory Limit (memory_limit) Success 768M
Maximum Execution Time (max_execution_time) Success 120
PHP register_globals (register_globals) Success Off (False)
PHP output_buffering (output_buffering) Success On
disable_functions in PHP (disable_functions) Success
PHP Open Basedir (open_basedir) Success
Test for remote URL (test_remote_url) Success Success
fsockopen: Connection ok! Success
fopen: Connection ok! Success
File uploads (file_uploads) Success On (True)
Maximum Post Size (post_max_size) Success 128M
Maximum Upload Size (upload_max_filesize) Success 128M
Session Save Path (session_save_path) Success /tmp (0755)
Sessions are allowed to use Cookies (session_use_cookies) Success On (True)
Basic XML (expat) support (xml_function) Success On (True)
Checking for the XMLReader class (xmlreader_class) Success On (True)
Test ini_set (check_ini_set) Success On (True)
Test for the curl library (curl) Success On
Test curl version (curlversion) Success version 7.59.0, minimum recommended version is 7.19.7

Server Information
Server Software (server_software) apache/2.4.29 (unix) mod_hive/6.27 openssl/1.0.1e-fips mod_fastcgi/2.4.6
Server API (server_api) cgi-fcgi
Server Operating System (server_os) linux 3.12.18-clouder0 on x86_64
Server Database (server_db_type) mysql (mysqli)
Server Database Version (server_db_version) Success 5.6.36
Check database access levels (server_db_grants) Success found a "grant all" statement that appears to be suitable

In the selfreg settings there is an option entitled "Automatically create users in the FEU module".

If you want to manually verify users before they are able to login, this should be set to 'no'.

Thank you for your response CalGuy!

When I set the "Automatically create users in the FEU module" to "No"

I then do not know when a user has submitted the registration form unless I periodically login and check the Self Reg mod for new user entries. There is no message sent to the admin when a user completes the self reg unless I leave the "Automatically create users in the FEU module" set to "Yes" then the admin receives the "New Registration" notification but the user is already authorized to see the content before I can verify them.

I created a work around by creating an "authorized" group and an "unauthorized" group and set the self reg form to add new users to the "unauthorized" group and "Automatically create users in the FEU module" to Yes, then when a user signs up, I receive a "New Registration" notification and then I go in and change the user's group from "unauthorized" to "authorized" unfortunately when I change the user's group there is no way for the user to know they have been authorized as they do not receive a notification that they have ever been authorized with or without my workaround.

I have one more question...can the FEU mod send an email notification to a user when the user has been added or removed from a group?