- 🇩🇪Germany D34dMan Hamburg
Thanks for the contribution. Closing this issue as focus is now on Drupal 10 release. You may follow 📌 Port PM to Drupal 10 Active to know more.
From #2762511-11: Incorrect dates after upgrading from storm-6.x-2.2 to pm-7.x-1.0-alpha5 → :
I did try upgrading pm-7.x-1.0-alpha5 to pm-7.x-2.2 and now the start/end times have shifted backward 6 hours. For example June 28, 2016 - 09:15 to 09:30 was converted to June 28, 2016 - 03:15 to 03:30.
From #2762511-14: Incorrect dates after upgrading from storm-6.x-2.2 to pm-7.x-1.0-alpha5 → :
Following up on the start/end time issue in pm-7.x-2.2:
I find the timetracking dates and times convert correctly from storm-6.x-2.2 to pm-7.x-1.0-alpha5 with the changes provided by D34dMan. But when I upgrade to pm-7.x-2.2 the dates are correct, but the start/end times are changed to be 7 hours earlier. Here are two examples:
07/04/2016 08:30 to 07/04/2016 08:45 --> 07/04/2016 01:30 to 07/04/2016 01:45
06/14/2016 08:30 to 06/14/2016 16:15 --> 06/14/2016 01:30 to 06/14/2016 09:15
After D34dMan's suggestion I checked my time zone settings. The default time zone is UTC -7 in Drupal 6, after I upgrade core it somehow changes to UTC -6 in Drupal 7. I manually reset the default time zone to UTC -7, run the Storm to PM upgrade (including the patch) and my timetrackings are converted with the correct date and time. Then I download the latest PM, update the database, and the timetrackings have the correct date, but the start/end times are 7 hours early.
Closed: outdated
2.2
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thanks for the contribution. Closing this issue as focus is now on Drupal 10 release. You may follow 📌 Port PM to Drupal 10 Active to know more.