sorry but I got a Problem with the usage of Password in Community Builder

OK, but on CB the Password Culomn is needed because you cant delete it it says systemvariable are not able to be deletet. so I was thinking that CB is needing it. But we figured something out. And maybe in future versions it will be Easyer in that kind of situation  

There is no password column in _comprofiler and if there is one you should delete it as it's not a part of our table structure. It should exist exclusively in _users. Joomla's LDAP authentication plugin should be storing a password with the account as the _users table and Joomla user object require one. At any rate I've a ticket to look into this for a future release to see what could be going wrong.

krileon wrote:

There is no password column in _comprofiler and if there is one you should delete it as it's not a part of our table structure. It should exist exclusively in _users. Joomla's LDAP authentication plugin should be storing a password with the account as the _users table and Joomla user object require one. At any rate I've a ticket to look into this for a future release to see what could be going wrong.

• I have no password column in _comprofiler
• I use a custom sync . 
• The joomla password is empty.

In Joomla 3

• Edit user with empty password save with Joomla OK
• Edit user with empty password save with CB OK

 
Upgraded to Joomla 5

• Edit user with empty password save with Joomla OK
• Edit user with empty password save with CB error.

CB seems more strict in J5 then Joomla itself even when the field is not touched.
If a moderator want to edit a CB profile field of a user with empty password in the frontend they also get the password error. 
 

Disable your custom sync plugin and see if your issue persists. As far as I'm aware and in my tests you cannot have a user in Joomla with an empty password. Even Joomla's LDAP plugin will randomly generate them whether it's used or not. Will create a test account and null the password to explore this further and see if there's a check we can add to avoid this issue or generate them a password.

Ok, was able to confirm the issue by emptying the password column for a user in _users. Will review accounting for this in CBs storage.

Ok, a fix is pending review. Once merged will release a new CB build release fixing this. Tested backend and frontend saving of profile with empty password.

forge.joomlapolis.com/issues/9653