I have debugged this issue until I got to a suspected cause. I am using Joomla 1.5.9 and CB 1.2 with the LDAP plugins by Sam Moffatt.
The call stack on login looks like:
administrator/components/com_comprofiler/library/cb/cb.tables.php.moscomprofilerUser->_loadBy_field : lineno 768
administrator/components/com_comprofiler/library/cb/cb.tables.php.moscomprofilerUser->loadByUsername : lineno 725
components/com_comprofiler/comprofiler.php.login : lineno 1611
components/com_comprofiler/comprofiler.php.require_once : lineno 132
libraries/joomla/application/component/helper.php.JComponentHelper->renderComponent : lineno 162
includes/application.php.JSite->dispatch : lineno 124
index.php.{main} : lineno 68
On line 764 of cb.tables.php we set an SQL query which looks like:
$query = SELECT * FROM #__users AS u LEFT JOIN #__comprofiler AS c ON c.id = u.id WHERE
u.`username` = 'dragon' LIMIT 1
When I get $arr back from loadAssoc() on line 766, it has the "id" field as <Uninitialized>.
Further up the stack in comProfiler.php I try to use this data in a $row->store() call to synchronize the comprofiler table with confirmed and approved set. Unfortunately, since the "id" is the table key, the store() fails.
By the way, if I run the same SQL query in phpMyAdmin, I get the same data back, but the "id" is correctly set.
Any suggestions on how to fix this?
Any Ideas?
Post edited by: eeDragon, at: 2009/03/13 21:50
Post edited by: eeDragon, at: 2009/03/17 02:01