Anonymous Login
2022-09-26 16:27 PDT

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000860v2.4 Release (Closed)[All Projects] Generalpublic2011-08-16 23:38
Assigned Tocaseydk 
Product Version 
Target VersionFixed in Version2.4 
Summary0000860: LDAP failed with error: "contact owner is not set"
Description(I had a thread open at the Forum asking the same question, but did not get any response back. So I posted here again for better visibility. Sorry for the duplication. This is an urgent issue for us).

I have recently installed web2project, and enabled LDAP. However, the LDAP login never works, and it complains:

modules\contacts\contacts.class.php(92): CContact::store-check failed - contact owner is not set

This is an error during user creation. web2project authenticate the user against LDAP, and succeeded. It then tried to create a user in its database, but failed with the above message.
TagsNo tags attached.
Attached Files




caseydk (administrator)

Resolved in r1984, will be in next release;


lzhongsh (reporter)

How big is the code change? Can you send it to me so I can fix myself and not waiting for the next release? We need it working ASAP.


caseydk (administrator)

One line:


lzhongsh (reporter)

I finally got a chance to try this fix out. It seems moves one step further. Now I am getting:

contacts.class.php(115): CContact::store failed Out of range value for column 'contact_owner' at row 1

I debugged through it, and found that the value of "contact_owner" is set to -1. It seems like coming from "$AppUI->user_id". I am curious, what is $AppUI->user_id?

Any help greatly appreciated!


caseydk (administrator)

Just within the createsqluser method, you may need this line:

global $AppUI;


lzhongsh (reporter)

I have this line in that function. See attached code.

I tried hard coding contact_owner to 1, and it works, but I don't know if it is OK to hard code.


lzhongsh (reporter)

Any comments? What is "contact_owner" used for? Is it OK to hard code it to 1?


caseydk (administrator)

Yes, hard code it to whatever your ID is.

This is closed in the pending release.. which will become the actual release (and solve your problems) if people stop complaining that they have problems.

-Issue History
Date Modified Username Field Change
2011-07-05 11:04 lzhongsh New Issue
2011-07-14 23:08 caseydk Project v2.3 Release (Closed) => v2.4 Release (Closed)
2011-07-14 23:10 caseydk Note Added: 0002029
2011-07-14 23:10 caseydk Status new => resolved
2011-07-14 23:10 caseydk Resolution open => fixed
2011-07-14 23:10 caseydk Assigned To => caseydk
2011-07-14 23:17 lzhongsh Note Added: 0002030
2011-07-14 23:17 lzhongsh Status resolved => feedback
2011-07-14 23:17 lzhongsh Resolution fixed => reopened
2011-07-14 23:32 caseydk Note Added: 0002033
2011-07-14 23:32 caseydk Status feedback => resolved
2011-07-14 23:32 caseydk Resolution reopened => fixed
2011-07-25 21:46 lzhongsh Note Added: 0002083
2011-07-25 21:46 lzhongsh Status resolved => feedback
2011-07-25 21:46 lzhongsh Resolution fixed => reopened
2011-07-30 15:21 caseydk Note Added: 0002093
2011-07-30 15:21 caseydk Status feedback => resolved
2011-07-30 15:21 caseydk Resolution reopened => fixed
2011-07-30 15:34 lzhongsh Note Added: 0002096
2011-07-30 15:34 lzhongsh Status resolved => feedback
2011-07-30 15:34 lzhongsh Resolution fixed => reopened
2011-07-30 15:34 lzhongsh File Added: LDAP.class.php
2011-08-01 14:56 caseydk Status feedback => resolved
2011-08-01 14:56 caseydk Resolution reopened => fixed
2011-08-01 15:26 lzhongsh Note Added: 0002104
2011-08-01 15:26 lzhongsh Status resolved => feedback
2011-08-01 15:26 lzhongsh Resolution fixed => reopened
2011-08-01 18:10 caseydk Note Added: 0002105
2011-08-01 18:10 caseydk Status feedback => resolved
2011-08-01 18:10 caseydk Resolution reopened => fixed
2011-08-01 18:15 caseydk Note View State: 2105: public
2011-08-16 23:38 caseydk Status resolved => closed
2011-08-16 23:38 caseydk Fixed in Version => 2.4
+Issue History