Hello, I downloaded latest release (which was released on June 21) and updated my module. This issue was discussed before and thought there was a fix in this release.

This only happends when a new user logs in and profile is turned on.

Are you planning to support CAS while profile module is on?

This issue was discussed at:
http://drupal.org/node/124207
http://drupal.org/node/130480

* warning: array_keys(): The first argument should be an array in /my/drupal/directory/modules/user/user.module on line 361.
* warning: implode(): Bad arguments. in /my/drupal/director/modules/user/user.module on line 361.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1 query: SELECT DISTINCT(p.perm) FROM role r INNER JOIN permission p ON p.rid = r.rid WHERE r.rid IN () in /my/drupal/directoy/includes/database.mysql.inc on line 180.

Comments

metzlerd’s picture

metzlerd commented

Yes, I don't know how or why this keeps cropping back up. I'll try and figure this out. I'm beginning to suspect a problem with the CVS client I'm using.

Dave

metzlerd’s picture

metzlerd commented
Assigned: Unassigned » metzlerd
metzlerd’s picture

metzlerd commented

Ok, I cannot reproduce this problem. With a freshly downloaded copy of the 5.x-2.1 release. I have the profiles module enabled and was able to create a user account successfully.

I've compared the realeased code with the head code and they are identical. I guess that I'm back to the drawing board a bit.

I hand inspected the code for the fix that I put in (to load user 1 when creating accounts) and it's in there.

Do I recall correctly that you are using Multi-site? Perhaps there's another case related to that.

One more thing. Do you still have a user in with a uid of 1? You haven't deleted it or done anything odd with permissions on this site have you?

Guess I'm back to looking into how to reproduce this.

Trying to figure out how to help.....

shino’s picture

shino commented

Ok, I was wrong with what it was conflicting with. I deleted module files and replaced with brand new files to see if I did not update the files correctly. Well, it still gives me same error & warnings. So I tried with profile off, and it still gave me same error & warning.

I'll turn all module off and I'll test one at a time to see which one is causing it to produce this error...

I'll post my findings.

Thank you

shino’s picture

shino commented

I believe buddylist is the one may be causing this warning messages. I disabled buddylist and tried few times to be sure. Warning was gone once I disabled buddylist...

So, I'm assuming I'm on my own for this one...

metzlerd’s picture

metzlerd commented

I'll help as much as I can. On thing to try would be to adjust the weight of the CAS module. See if you can get it to load before Buddy-list. This may help. From the mysql prompt:

update system set weight=-1 where name='cas';

This should force CAS to fire before buddy-list. I don't know for sure that this will affect the problem, but it might.

I'm about to leave on a trip in about a week, and am pretty busy, but if I have time I'll try out the module combination. The way that I found this in profile was to hack the profile module with debug statements until I found what was going on. It's tedious, but if you're comfortable sprinkling drupal_set_message or watchdog statements in the code, it can be enlightening.

Dave

shino’s picture

shino commented

I've tried with your database suggestions, but did not make any differences. I will do some digging and will post you with findings. Have a great vacation. I hope I can have something to report back by the time you get back :D

shino’s picture

shino commented

Just to give you an update. I have not found a cure yet...

metzlerd’s picture

metzlerd commented
Version: 5.x-2.1 » 5.x-3.0
Status: Active » Fixed

Believe this is fixed with caching support in 5.x-3 and 6.x

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.