Closed (fixed)
Project:
Date
Version:
6.x-2.4
Component:
Date Timezone
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 May 2010 at 15:30 UTC
Updated:
13 May 2012 at 18:49 UTC
This message keeps coming up whenever a user logs in.
Here is the full error message:
user warning: Unknown column 'timezone_name' in 'field list' query: UPDATE users SET timezone_name = 'America/New_York', timezone='-14400' WHERE uid = 32 in /sites/all/modules/date/date_timezone/date_timezone.module on line 249.
Comments
Comment #1
abasso commentedSame here, any updates on this?
Comment #2
doublejosh commentedMe too. No column in the db. Will try turning timezone support on and off again after a little more grant permission given.
Did an uninstall and reinstall, placed the column :)
However still curious about why Date API chooses to place a timezone_name field in the user table.
Shouldn't that just be a foreign ID key, like the already existing timezone field? Why would the architecture call for a string, seems wasteful and bad normalization.
Am I missing something?
Sorry for cross posting this question in two threads.
Comment #3
timos commentedHi same here !
I temporaly solved the problem setting off the User-configurable time zones, but it's not a long term solution.
I didn't try more and neither to read date_timezone module code.
Comment #4
karens commentedThere is an update hook that creates that field. If you didn't run the update the table will be missing the field. You can disable and uninstall and then re-install the module if you don't need to preserve any data, or run update.php to be sure all the updates have run. If you still don't have the field, you can add it manually.
Comment #6
doublejosh commentedFollow up: believe D7 has new architecture for user timezones.
D6 had both a timezone column (in seconds) and a timezone_name as a string.
D7 now have just the timezone column, but it's the string.