cowboysdude wrote:
krileon wrote:
lukass2000 wrote:
Hello!
Is there a possibility the original login module (mod_login) to completely disable?
I do not know why, but sometimes applications are on the original module, and not on the CB login.
THANK YOU!
Disable (unpublish) Joomlas login module then publish CB Login.
That does NOT always work...
Not always, but the case generally is users continue to operate both login modules and registration systems at the same time. This will, has, and does cause severe conflicts or unknown reactions.
Unpublish the original login module entirely. Configure global settings off and have CB registration independent of joomla. I've repeatedly attempted to duplicate these issues and have not been successful after following proper configuration procedures.
J1.0:
Site -> Global Configuration -> Site
Allow User Registration: NO
Use New Account Activation: NO
Front-end Login: NO
Require Unique E-mail: (your choice.. affects CB!)
Components -> Community Builder -> Configuration -> Registration
Allow User Registration: yes, independently of global setting
(rest is your choice)
Modules -> Site Modules
Login Form (mod_login): UNPUBLISHED
CB Login (mod_cblogin): PUBLISHED
J1.5:
Site -> Global Configuration -> System
Allow User Registration: NO
New User Account Activation: NO
Components -> Community Builder -> Configuration -> Registration
Allow User Registration: yes, independently of global setting
(rest is your choice)
Extensions -> Module Manager
Login Form (mod_login): UNPUBLISHED
CB Login (mod_cblogin): PUBLISHED
Give that a try; and remember documentation is there to help everyone for this and many other basic scenarios.