Profil: updated to Commerce Kickstart 7.x-2.8 before was version from februar-march Commerce Kickstart 7.x-2.4
Core: Drupal 7.22 before update Drupal 7.20
PHP 5.4.4-14 | PHP DOM extension: enabled | PHP register globals: disabled | PHP extensions: enabled | cURL: enabled
Database: Mysql 5.5.31-0+wheezy1 | Web server: Apache/2.2.22 (Debian)
Expecting: getting actual time and date in time zones, orders, emails.
Instead getting: incorrect time in orders, emails, time zones like 2.3.1905, 29.5.2018, 15.10.2025, 1.7.1907. Time is incorrect too. As you can see in screenshot date and times few hour before was 1907 and now was 1908( as well time and day is now different )
Note: Other PHP applications have correct time. If I try new Date and echo it all is as it should be. I google it and look at issues and bugs with date topic but no luck. I hope someone can help me.
Comment | File | Size | Author |
---|---|---|---|
timebug.png | 34.37 KB | nemesisqo |
Comments
Comment #1
Jooblay.net CreditAttribution: Jooblay.net commentedAny thing in your log?
Are you running drush?
Comment #2
marcingy CreditAttribution: marcingy commentedThis is not a critical core bug and is likely a config issue.
Comment #3
nemesisqo CreditAttribution: nemesisqo commentedfrom your view its normal, but imagine that one order was sent to customer like 1907 before like 2018, do you know how thats look from customer site ? when you look at orders and dates are total off. some this year other this year(days and months are off too). So from my I select critical. I think this is maybe connected to drupal getting time object on php 5.4.4 because on 5.3.1 I don't have this issue. I reproduce this error only on this php version. its not related to db that i checked.
Can you suggest some solution or ho to set this?
Comment #4
nemesisqo CreditAttribution: nemesisqo commentedi have only ftp access to site from my hosting. So far nothing.
Comment #5
Jooblay.net CreditAttribution: Jooblay.net commentedBefore you start any of the below make sure you have a working backup.
Check your log at http://example.com/admin/reports/dblog
Check your status page @ http://example.com/admin/reports/status
Then check your file permissions.
Then check all date, calendar modules to make sure they are not corrupted when you enabled them. Disable them and test. You may also want to disable them and uninstall them to wipe the database. **Warning** when you uninstall the module you loose all associated date.
You will also want to clear your site cache and make sure caching is disabled for all testing.
Lastly look for other errors in your log and site wide.
The reason why this is not critical is because no one else is reporting the issue. Meaning it is on your end in the configuration. (General rule of thumb) I also moved this from a bug to a support request until we have more information about this issue.
Hope that helps...
Comment #6
Jooblay.net CreditAttribution: Jooblay.net commentedWow this PHP 5.4.4-14 could be your issue right out of the gate. I would look for similar issues caused by 5.4 we have not gone past 5.3 on all our hosting servers.
Comment #7
nemesisqo CreditAttribution: nemesisqo commentedIt was some issue with hosting after wrote mail to him it was fixed but he did not explain what was issue if some php extension helped ( but php version on drupal is 5.4.4-14+deb7u2 maybe other pkg ), it would be nice if we could prevent this from happened to anyone. I tried to replicate this but on php website its little problem to get same version or on google. if i will get from him what was source of problem i will post it.
Comment #8
nemesisqo CreditAttribution: nemesisqo commentedleseen: cannot get logs with that time but i thing at that time was problem with updates too because website write like last update 5years ago. After I update all admin/reports/status was all ok but time and date was still off. I tried to clear cache and turn off that did't help. file permissions was ok too as before error appeared. But js things like date pikers was ok.
Comment #9
Jooblay.net CreditAttribution: Jooblay.net commentedGreat work:)
Do you think we can close this ticket?