Download & Extend
Bakery Single Sign-On System » Issues

The timezone in the sub-domain is not synchronized with the value in the master domain

Posted by kiamlaluno on November 19, 2009 at 7:25pm
Project:Bakery Single Sign-On System
Version:7.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

I have noticed that my account on g.d.o still says America/New York, which is the value I have set when I was in USA. When I came back to Italy, I have changed the timezone on Drupal.org, and it should have been changed in g.d.o as well.

I can fix the timezone, that is not a problem. I am just pointing out this to let others know there is probably an issue.

Login or register to post comments

Comments

#1

Posted by kiamlaluno on November 19, 2009 at 7:27pm
Project:Drupal.org webmasters» Drupal.org infrastructure
Component:Groups.drupal.org» groups.drupal.org

I am changing the issue queue, just in the case this is related with the problem caused by Bakery.

#2

Posted by kiamlaluno on November 19, 2009 at 7:34pm

When I change the timezone on d.o, I get this message:

Successfully updated account on localize.drupal.org.
Successfully updated account on Drupal API.
Successfully updated account on docs.drupal.org.
Successfully updated account on groups.drupal.org.
Successfully updated account on Drupal Association.
The changes have been saved.

That is not actually true, as g.d.o still was showing the timezone before the change.

I tried again by setting the timezone to UTC, and the change was not propagated to g.d.o.

#3

Posted by greggles on November 19, 2009 at 7:41pm

That is a feature of bakery and it is enabled on both sites, so I think it is a bakery bug.

#4

Posted by kiamlaluno on November 19, 2009 at 7:49pm
Title:The timezone is not synchronized with the value set in Drupal.org» The timezone in the sub-domain is not synchronized with the value in the master domain
Project:Drupal.org infrastructure» Bakery Single Sign-On System
Version:<none>» 7.x-1.x-dev
Component:groups.drupal.org» Code

I thought that maybe the timezone was the only setting that was not synchronized, for some reasons.

I am moving the report in the project issue queue.

#5

Posted by BenMirkhah on November 21, 2009 at 12:08am

My tweak on a similar issue almost works on timezone: http://drupal.org/node/556666

Only problem is that you have to do it twice for it to work =)

#6

Posted by coltrane on April 13, 2011 at 9:05pm

Is this still an issue?

nobody click here