Answers.Body: <p>I just created this simple function in my custom extensions service</p>
  
  <pre><code> public function getTimeByZone(\DateTime $time, $zone)
  {
  
      $timeZ = new \DateTime($time-&gt;format('H:i:s'), new \DateTimeZone('UTC)'));
      $timeZ-&gt;setTimezone(new \DateTimeZone($zone));
      return $timeZ;
  
  }
  </code></pre>
  
  <p>Where:</p>
  
  <p>-$time is the UTC stored datetime object
  -$zone is the user's time zone, for instance, CET</p>
  
  <p>To call it from twig, in my case would be:</p>
  
  <pre><code>{{  getTimeByZone(dateObject, app.request.headers.get('timezone')) | date( 'H:i') }}
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-06-22T11:25:36.853Z
Answers.LastActivityDate: 2017-06-22T11:25:36.853Z
Answers.UserDisplayName: Ibon Conesa
Answers.Body: <p>I wouldn’t recommend hacking the MySQL timezone, since that would happen on a global basis, not just for the current user, and will result in some weird race conditions whenever two people are using the site/CP at the same time.</p>
  
  <p>Getting an entry to go live at a certain time based on their time zone is a fundamentally different thing than the feature provided by entry Post Dates. So your best bet here is to code the functionality yourself, rather than trying to bend Post Dates into something they’re not.</p>
  
  <p>To do that, you should create your own custom Date/Time field to hold the post dates. Give it a handle that’s different than “postDate” so you don’t run into naming conflicts in your templates - let’s say it’s “liveDate”.</p>
  
  <p>In your templates, you can query against your liveDate field like so:</p>
  
  <pre class="lang-twig prettyprint-override"><code>{% set timezone = 'Europe/Paris' %}
  {% set localDate = date()|date('Y-m-d H:i:s', timezone) %}
  {% set entries = craft.entries.section('blog').liveDate('&lt;=' ~ localDate) %}
  </code></pre>
  
  <p>That will only give you entries where the liveDate field is before or equal to the current date/time, in whatever timezone you’ve passed in.</p>
  
  <p>Couple gotcha’s:</p>
  
  <ul>
  <li>Twig’s <a href="http://twig.sensiolabs.org/doc/filters/date.html" rel="nofollow">|date</a> filter requires that you specify the timezone using one of PHP’s supported <a href="http://php.net/manual/en/timezones.php" rel="nofollow">timezone names</a>, not a numeric offset. Your script that is determining the timezone based on the user’s IP will need to account for that.</li>
  <li>The built-in Post Date fields will still be enforced, so you will need to get in the habit of making sure those are set at least 14 hours before the custom liveDate field is set (UTC-14 is the earliest time that “tomorrow” begins). That’s assuming you’ve left your system timezone set to UTC in Settings > General.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-08T14:32:43.853Z
Answers.LastActivityDate: 2014-10-23T20:10:46.573Z
Answers.LastEditDate: 2014-10-23T20:10:46.573Z
Answers.UserDisplayName: Brandon Kelly
Body: <p>I've done a bunch of research and I can't seem to find a suitable answer for this issue without hacking which I'd like to avoid.</p>
  
  <p>My client needs the entries in the DB to always assume they're relative to the users current timezone. So content set to display at 9am on Monday morning will display at 9am Monday in every timezone.</p>
  
  <p>The locale options in Twig only adjust the UTC timestamp to the users current timezone but it's still displaying content based on UTC timestamp in the DB.</p>
  
  <p>Through MySQL I can use the following command per session to accomplish what I'm looking for:</p>
  
  <pre><code>SET SESSION time_zone = '+10:00';
  </code></pre>
  
  <p>This appropriately offsets the MySQL time to match a users timezone +10 hours ahead of UTC, in this case Australia.</p>
  
  <p>Reading <a href="http://www.yiiframework.com/wiki/197/local-time-zones-and-locales/">this article</a> it seems that "initSQLs" might be the answer but it's a Yii article that talks about adding that command to the <em>db</em> array within the protected/config/main.php file which I'm unsure of how to tie into.</p>
  
  <p>Nevertheless, I'm hoping someone might have some insight into how I can bootstrap the DB calls per user session or another solution potentially utilizing a plugin.</p>
  
  <p>We're doing timezone lookups by IP address, I realize the potential issue, so the option will need to work for both logged in and logged out users.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-07T23:33:41.013Z
Comments.Text: Are you referring to dates/times in the control panel or on the front-end?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-08T14:02:20.943Z
Comments.Text: Only what's displayed on the front-end.
Comments.UserDisplayName: Alex Rubin
Tags: <datetime><postdate>
Title: Adjust all date/times to users current timezone
ThreadText: # Adjust all date/times to users current timezone
  
  (Asked by: username_0 on 2014-10-07)
  
  I've done a bunch of research and I can't seem to find a suitable answer for this issue without hacking which I'd like to avoid.
  
  My client needs the entries in the DB to always assume they're relative to the users current timezone. So content set to display at 9am on Monday morning will display at 9am Monday in every timezone.
  
  The locale options in Twig only adjust the UTC timestamp to the users current timezone but it's still displaying content based on UTC timestamp in the DB.
  
  Through MySQL I can use the following command per session to accomplish what I'm looking for:
  
  ```
  SET SESSION time_zone = '+10:00';
  
  ```
  
  This appropriately offsets the MySQL time to match a users timezone +10 hours ahead of UTC, in this case Australia.
  
  Reading [this article](http://www.yiiframework.com/wiki/197/local-time-zones-and-locales/) it seems that "initSQLs" might be the answer but it's a Yii article that talks about adding that command to the *db* array within the protected/config/main.php file which I'm unsure of how to tie into.
  
  Nevertheless, I'm hoping someone might have some insight into how I can bootstrap the DB calls per user session or another solution potentially utilizing a plugin.
  
  We're doing timezone lookups by IP address, I realize the potential issue, so the option will need to work for both logged in and logged out users.
  
  **Tags:** datetime, postdate
  
  > **Comments:**
  > **username_1**: Are you referring to dates/times in the control panel or on the front-end?  
  > **username_0**: Only what's displayed on the front-end.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2014-10-08. Score: 6 | Accepted answer
  
  I wouldn’t recommend hacking the MySQL timezone, since that would happen on a global basis, not just for the current user, and will result in some weird race conditions whenever two people are using the site/CP at the same time.
  
  Getting an entry to go live at a certain time based on their time zone is a fundamentally different thing than the feature provided by entry Post Dates. So your best bet here is to code the functionality yourself, rather than trying to bend Post Dates into something they’re not.
  
  To do that, you should create your own custom Date/Time field to hold the post dates. Give it a handle that’s different than “postDate” so you don’t run into naming conflicts in your templates - let’s say it’s “liveDate”.
  
  In your templates, you can query against your liveDate field like so:
  
  ```twig
  {% set timezone = 'Europe/Paris' %}
  {% set localDate = date()|date('Y-m-d H:i:s', timezone) %}
  {% set entries = craft.entries.section('blog').liveDate('<=' ~ localDate) %}
  
  ```
  
  That will only give you entries where the liveDate field is before or equal to the current date/time, in whatever timezone you’ve passed in.
  
  Couple gotcha’s:
  
  * Twig’s [|date](http://twig.sensiolabs.org/doc/filters/date.html) filter requires that you specify the timezone using one of PHP’s supported [timezone names](http://php.net/manual/en/timezones.php), not a numeric offset. Your script that is determining the timezone based on the user’s IP will need to account for that.
  * The built-in Post Date fields will still be enforced, so you will need to get in the habit of making sure those are set at least 14 hours before the custom liveDate field is set (UTC-14 is the earliest time that “tomorrow” begins). That’s assuming you’ve left your system timezone set to UTC in Settings > General.
  
  
  ---
  
  ### Answer by username_2 on 2017-06-22. Score: 1
  
  I just created this simple function in my custom extensions service
  
  ```
   public function getTimeByZone(\DateTime $time, $zone)
  {
  
      $timeZ = new \DateTime($time->format('H:i:s'), new \DateTimeZone('UTC)'));
      $timeZ->setTimezone(new \DateTimeZone($zone));
      return $timeZ;
  
  }
  
  ```
  
  Where:
  
  -$time is the UTC stored datetime object
  -$zone is the user's time zone, for instance, CET
  
  To call it from twig, in my case would be:
  
  ```
  {{  getTimeByZone(dateObject, app.request.headers.get('timezone')) | date( 'H:i') }}
  
  ```
  
  
  ---
  
  