Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I ahve just tried updating the time info on my site to BST (+1 hour) for the drupal settings, but for some reason that makes Tribune be ahead by a further hour for the time it shows.
Another oddity - changing the timezone (which I reverted back to UTC) has broken the highlight thingy where having a timestamp in a post no longer highlights the corresponding message.
Comments
Comment #1
naheemsays commentedAbout the timestamp highlighting - it seems that the change in clocks has confused it and is trying to quote messages from an hour earlier.
Weird thing is I have gone back to UTC so I have no idea what it (and tribune) is basing its time decisions on
Looking at the source at two posts linking the same time, one with working highlighting, the other with not working highlighting, I noticed that the one with not working highlighting has
ref=""ie no referenced post id.Comment #2
naheemsays commentedA further comment - In tribune.module I have used find and replace to change all instances of
gmdatetodateand that has fixed the highlighting problem for new posts, but it still does not show the correct time with the posts as set by the timezone.Comment #3
naheemsays commentedHm... I have now removed the changes and it still seems fixed?
Weird. it was broken for over an hour, I made the changes, and it was fixed. removed them and it remain fixed.
leaving active as you may have more of a clue.
Comment #4
SeeSchloss commentedHmm... changing gmdate to date should break highlighting unless your site's timezone is UTC. Post dates are saved as UTC timestamps in the database, and the site's default timezone (in admin/settings/date-time) is then used for display, and for matching references. It means old references should still work when you change your site's timezone, and new references should work too... however, if you use the "parse visible messages again", the old references will be lost (as they won't match anymore the new hours).
There wouldn't be these problems if Drupal used timezones like Europe/Paris or America/Montreal, rather than fixed "UTC+1" or "UTC-5" offsets, without that there is really no mean to know when the time changed, unless I save the timezone of each post along with its time, which sounds like quite a waste for an event that only happens once or twice a year (I'm not sure all these problems arise when switching to winter time).
Anyway, as long as you don't hit "parse visible messages again" while there are still visible messages which reference posts with the old timezone, nothing should break, really.
Comment #5
naheemsays commentedThe problem did eventually fix itself (unless I poked something that I am unaware of...), maybe it was just the server being confused between 1 and 2 am (GMT)? it seemed to fixed itself after an hour.
Comment #6
SeeSchloss commentedI don't really know, my own tribune has switched quite a few times between UTC-4/UTC+2 and UTC-5/UTC+1 and I have never noticed a problem, but it may be different when there's more than 1 hour difference, too... well...