uddeIM 1.1 released

using Joomla 1.5.2, Uddeim 1.1, and CB 1.2 I get the following error when I try to delete a user from the CB user manager.

Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ')' in /home/myname/wwwroot/mysite.com/components/com_uddeim/cb_extra.php on line 19

That line is...

function user_delete_ext($user->id,$pmsUserDeleteOption) {

any ideas on what might be wrong? I'm stumped at the moment.

scubaguy wrote:

Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ')' in /home/myname/wwwroot/mysite.com/components/com_uddeim/cb_extra.php on line 19

That line is...

function user_delete_ext($user->id,$pmsUserDeleteOption) {

Damn, the first bug
Only appears with CB1.2 since a new plugin uses cb_extra.php.

Please remove "->", so the corrected line is
[code:1]function user_delete_ext($userid,$pmsUserDeleteOption) {[/code:1]

Fixed this in the package. I will release a hotfix for that when CB 1.2 is released.

Post edited by: slabbi, at: 2008/04/07 08:59

Hello again,

I found a bug which will keep from configuring Contact lists, but only when Joomla is not installed in the root but in a subfolder.

In userlists.php, in function uddeIMcreateLists, variable $pathtosite is used but not actually defined in the scope.

I corrected it by adding the following :

[code:1]function uddeIMcreateLists($myself, $item_id, $listid, $limit, $limitstart, $config) {
global $database;
// modification to make it work.
global $pathtosite;
// end of modification
[/code:1]

Post edited by: orion1024, at: 2008/04/09 17:08

Post edited by: orion1024, at: 2008/04/09 17:09

Confirmed.

Fixed in 1.2 and in the current package.

I will add this file to the maintenance package I release end of this month.

I found two more bugs in cb_extra.php

line 39 and 47 are missing each a "$" in "this->_setErrorMSG" it should be "$this->_setErrorMSG"

scubaguy wrote:

I found two more bugs in cb_extra.php

line 39 and 47 are missing each a "$" in "this->_setErrorMSG" it should be "$this->_setErrorMSG"

Confirmed. Thanks godness that is a bug that does only appear when the SQL statement fails and then the database error is the bigger problem