Something seems to be wrong with the part of my site's database that stores the different types of user roles. At first I noticed I couldn't seem to set anyone up as a certain type of user (called Contributing User)--the setting just wouldn't stick. Then I tried creating a new role and that seemed to just overwrite the Contributing User role. The setting still wouldn't stick, though, when I tried assigning users to this role. Then I tried again to add a new role, called Blogging User, and that just flat out didn't work. Can anyone out there help me try and track down the cause of this problem? It might've happened when we upgraded to Drupal 5.1.

Comments

manal’s picture

manal commented
Category: support » bug

I have the same problem with a website that I upgraded to drupal 5, even after I upgraded to drupal 5.3

I have an extra role that I cant edit or assign to any user. And when I try to add a new role I get a message "the role has been added" but it is not there.

amardini’s picture

amardini commented

When I checked the drupal logs, I found the following error:

Duplicate entry '0' for key 1 query: user_admin_role_submit INSERT INTO role (name) VALUES ('author') in /usr/local/www/apache22/data/ombudsman.website/includes/database.mysql.inc on line 172.

I found out that the 'role' table in MySQL had a default value of 0 and was *not* set to auto_increment.
I set it to auto_increment and everything worked fine then.

I think the cause of this is the migration script (or procedures).

drumm’s picture

drumm
he/him
Location NY, US
commented
Category: bug » support

The {sequences} table stores the next rid to be used in the roles table. All code adding roles should get a rid using db_next_id(). If this gets out of sync, manually update the id column in {sequences} and fix code which inserted the roles.

ricabrantes’s picture

ricabrantes commented
Status: Active » Closed (fixed)

No activity, Close..