- Output for 8.2.0 - 8.2.29, 8.3.0 - 8.3.26, 8.4.1 - 8.4.13
- Warning: ini_set(): Invalid date.timezone value 'dummy', using 'Europe/Amsterdam' instead in /in/Rli3e on line 3
- Output for 8.1.0 - 8.1.33
- Warning: ini_set(): Invalid date.timezone value 'dummy', we selected the timezone 'UTC' for now. in /in/Rli3e on line 3 Warning: DateTime::__construct(): Invalid date.timezone value 'dummy', we selected the timezone 'UTC' for now. in /in/Rli3e on line 4
- Output for 7.0.0 - 7.0.33, 7.1.0 - 7.1.33, 7.2.0 - 7.2.34, 7.3.0 - 7.3.33, 7.4.0 - 7.4.33, 8.0.0 - 8.0.30
- Warning: ini_set(): Invalid date.timezone value 'dummy', we selected the timezone 'UTC' for now. in /in/Rli3e on line 3
Fatal error: Uncaught Exception: DateTime::__construct(): Invalid date.timezone value 'dummy', we selected the timezone 'UTC' for now. in /in/Rli3e:4
Stack trace:
#0 /in/Rli3e(4): DateTime->__construct('now')
#1 {main}
thrown in /in/Rli3e on line 4
Process exited with code 255. - Output for 5.6.0 - 5.6.40
- Warning: ini_set(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. in /in/Rli3e on line 3
Fatal error: Uncaught exception 'Exception' with message 'DateTime::__construct(): Invalid date.timezone value 'dummy', we selected the timezone 'UTC' for now.' in /in/Rli3e:4
Stack trace:
#0 /in/Rli3e(4): DateTime->__construct('now')
#1 {main}
thrown in /in/Rli3e on line 4
Process exited with code 255.