+- webERP Forum (http://www.weberp.org/forum)
+-- Forum: webERP Discussion (http://www.weberp.org/forum/forumdisplay.php?fid=1)
+--- Forum: Problems / Bugs? (http://www.weberp.org/forum/forumdisplay.php?fid=8)
+--- Thread: 32-Bit Year 2038 Issue - Do We Care? (/showthread.php?tid=8299)
32-Bit Year 2038 Issue - Do We Care? - VortecCPI - 12-13-2018
BOMs.php
When adding a new BoM item...
The code below results in 12/31/1969:
PHP Code:
$_POST['EffectiveTo'] = Date($_SESSION['DefaultDateFormat'], Mktime(0, 0, 0, Date('m'), Date('d'), (Date('y') + 20)));
The code below results in 12/12/2037:
PHP Code:
$_POST['EffectiveTo'] = Date($_SESSION['DefaultDateFormat'], Mktime(0, 0, 0, Date('m'), Date('d'), (Date('y') + 10)));
Any ideas on this nonsense?
What the???
https://en.wikipedia.org/wiki/Year_2038_problem
More here: https://www.phpclasses.org/blog/package/10411/post/1-How-to-Implement-a-Year-2038-Problem-Fix-in-PHP-Applications-that-Are-Using-Unix-Timestamps.html
RE: 32-Bit Year 2038 Issue - Do We Care? - TimSchofield - 12-13-2018
I think this issue has been resolved in PHP7.
$_POST['EffectiveTo'] = Date($_SESSION['DefaultDateFormat'], Mktime(0, 0, 0, Date('m'), Date('d'), (Date('y') + 20)));
shows 12/13/2038 on my PHP7 machine.
tim