I set up a new site with Drupal 5.6
I enabled the Drupal module, enabled distributed authentication, and logged in with my drupal.id account.

Here's what I got:

warning: array_keys() [function.array-keys]: The first argument should be an array in /home/seasider/public_html/events/modules/user/user.module on line 378. 
warning: array_fill() [function.array-fill]: Number of elements must be positive in /home/seasider/public_html/events/modules/user/user.module on line 379. 
warning: implode() [function.implode]: Bad arguments. in /home/seasider/public_html/events/modules/user/user.module on line 379. 
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 /home/seasider/public_html/events/includes/database.mysql.inc on line 172.

Comments

johnnoc’s picture

johnnoc
Primary language Norwegian Bokmål
Location Oslo
commented

I think this is similar to the bug I encountered as well:

warning: array_keys() [function.array-keys]: The first argument should be an array in /home/xxxxx/public_html/sandbox/modules/user/user.module on line 378.
warning: array_fill() [function.array-fill]: Number of elements must be positive in /home/xxxxx/public_html/sandbox/modules/user/user.module on line 379.
warning: implode() [function.implode]: Bad arguments. in /home/xxxxx/public_html/sandbox/modules/user/user.module on line 379.
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 /home/xxxxx/public_html/sandbox/includes/database.mysql.inc on line 172.

I would also like to report that the user get logged in though.

mbria’s picture

mbria commented

Also happens with a 5.7 client VS a 5.7 master.

Exactly same warning message:

warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/drupal/modules/user/user.module on line 378.
warning: array_fill() [function.array-fill]: Number of elements must be positive in /var/www/drupal/modules/user/user.module on line 379.
warning: implode() [function.implode]: Bad arguments. in /var/www/drupal/modules/user/user.module on line 379.
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 /var/www/drupal/includes/database.mysql.inc on line 172.
mbria’s picture

mbria commented
Version: 5.6 » 5.7

Exactly same issue with two 5.7 sites.

Scenario:

* Apache 2
* PHP 5.2.1 (Running as fastcgi + suPHP)
* MySQL 5.0.38
* And as said, 5.7 master and 5.7 client.

Any case, looks like it's just a warn that could be hidden to final user, as far as user seams to successfully is log in.

bdragon’s picture

bdragon commented
Version: 5.7 » 5.x-dev

http://drupal.org/node/191803 marked dupe.
Changing version.

bart jansens’s picture

bart jansens commented

I thought we fixed this in 5.7, at least i can no longer reproduce this.

Does this happen with only core modules enabled, or in combination with specific contrib modules?

ooz’s picture

ooz commented

Same setup, same error.

I disabled the skype-support-module and no more errors.

joachim’s picture

joachim commented

I'm not using that module.

I don't remember if I had only core modules when I got that error, but at any rate the only contrib modules I now have on that site are Views, CCK, easylists, and JS Calendar.

ekes’s picture

ekes commented

Unless I'm mistaken it's fixed in -dev not 5.7 but it is fixed as per http://drupal.org/node/165642

bart jansens’s picture

bart jansens commented
Status: Active » Fixed

Indeed, i got the versions mixed up, its fixed in 5.8.

Anonymous’s picture

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

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