The default time can now be set by the admin (see #1069668: Default time with user override) but we have not discussed timezone considerations. Currently the default time offset will be that many hours/minutes according to the server clock. If the site has a timezone which differs from GMT and/or the users timezones are configurable, should we make any adjustments to the time at the point of storing in admin and/or when being used in the node edit form?
If an admin sets a default time, and two users use that time, but the users are in different timezones, their posts will be published at different times. I'm not saying this is wrong, just that we should discuss what we mean by 'default time'.
Comments
Comment #1
usaginyunyu commentedHi Jonathan1055
(If I understood your explanation in the right way)I think your "default" vision is correct.
If you have content creators in different time zones creating content for his timezone/country and scheduling it, I think they usually know best when they want the content to be published.
Comment #2
jonathan1055 commentedYes absolutely, you are right.
What I was considering is that if users (who are in different timezones) both use the default time as set by the admin, without altering it, then their nodes will be scheduled for different times. I was wondering whether we should convert the default time into the users timezone at the point when Scheduler writes 'The default time is ...' so that if the users do not enter a time and use the default, then the nodes are always scheduled for the same publishing time.
It may be fine just like it is - all I wanted was for some users in multi-zone sites to realise this, and maybe have a discussion on how they use the default time.
Comment #3
jonathan1055 commentedHaving thought about this more, and in light of the outcome of #2809627: Fix DefaultTime test for daylight-saving I think there is no need to alter the current behavior.