i have: Event 6.x-2.x-dev (2009-Mar-15)

through the magic of SVN i have narrowed down that it is this module that breaks my being able to set a user's role.

i see there is a 1 day newer dev version, i'll try that.

failing that, i'll see what the _user hook code looks like in this module as that's like where the issue lies.

Comments

liquidcms’s picture

oops.. nope my bad.. i do have the latest.. and it's busted.. :(

liquidcms’s picture

ok, i'm lost.. only thing dependent on event right now in my setup is og_calendar, and makes no difference if it is enabled or not, if event is enabled, roles is busted.

i even renamed all the event_ functions to something else and still busted - but very repeatable - disable event and roles works again.

liquidcms’s picture

Status: Active » Needs review

sorted it out.. mostly

i think event module modifies how the user's timezone information is stored but ends up making the timezone value larger than the varchar 8 field that is allotted for this field in the user table.

in the user_save() function i get the save query with this: timezone = '116|-14400' , without event enabled the value is simply timezone = '-14400'. The insert fails and the user_save function bails.

and update script is required to increase the size of this field in the user table.

to test this i increased the field to varchar 16 and sure enough i can now set roles again.

I can do up a patch for this if anyone can verify this bug.

killes@www.drop.org’s picture

I don't think that event.module should try to save timezone = '116|-14400' it should try to save -14400 as the timezone and 116 in the timezone_id column that it has created for this purpose.

killes@www.drop.org’s picture

Status: Needs review » Postponed (maintainer needs more info)

I have tried this with TZ 456 (which also has -14400) and it works there.

Please provide more information.

japerry’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

Event for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.