[#2169] Auto Generate Password sends INCORRECT password.

Good day gentlemen.

Having a problem after upgrading from CB 1.2.3 to CB 1.3.1 and CBsubs 1.0.3 to CB 1.1.2

Registration Settings in CB:

Allow user registration -> YES (regardless of CB settings)
Autogenerate password -> YES
Require Admin Approval -> YES
Require e-mail Confirmation -> NO
AJAX USERNAME -> YES
AJAX EMAIL -> NO


now, I tried both by using the default pending approval message and the CBMAILS from incubator calling the [PASSWORD] field.

they DO BOTH give the same password (tested at same time)
but somehow this emailed password is NOT VALID.

could be a conflict between CBsubs and CB?

Post edited by: krileon, at: 2011/01/06 14:38

could be a conflict between CBsubs and CB?

No, a new password is generated after the user has been approved by the admin. Best approach is to remove the password from the PENDING email and add it to the Welcome email (this is the only scenario where this should be done). This should then give the user an accurate password after admin has approved them.

krileon wrote:

could be a conflict between CBsubs and CB?

No, a new password is generated after the user has been approved by the admin. Best approach is to remove the password from the PENDING email and add it to the Welcome email (this is the only scenario where this should be done). This should then give the user an accurate password after admin has approved them.

Makes sense.
Ill check that out... Thanks Krileon!.

Reviewing CB 1.3.1 source the password is generated in the following scenarios.

User Approval
User Confirmation
User Registration

HOWEVER, in backend for User Approval a password is only generated IF the user does NOT already have a password. As in the password column in _users database table would need to be empty. In other words; approve users from the frontend through the module and it should work how you're wanting.

This would appear to be a bug and have created a bug ticket so further investigate can be made. The password generated during first time registration should not be made invalid.

forge.joomlapolis.com/issues/2169