Project Planner HD is iPad version of Project Planner
FS#153 - Can not change month in calander
Attached to Project:
Project Planner HD
Opened by Don Damon (Trefton) - Warning: date(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Tuesday, 23 September 2014, 23:50 GMT+2
Last edited by Tomasz Wojtkowiak (TomekW) - Warning: date(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Friday, 10 October 2014, 12:27 GMT+2
Opened by Don Damon (Trefton) - Warning: date(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Tuesday, 23 September 2014, 23:50 GMT+2
Last edited by Tomasz Wojtkowiak (TomekW) - Warning: date(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Friday, 10 October 2014, 12:27 GMT+2
|
DetailsI was notified that my prior bug report was fixed with with recent update, this did populate the calander days(numbers) and I can choose a specific day in September but can not access any other month
There is no way to move from September to say October Prior task was: Thanks |
This task depends upon
Closed by Tomasz Wojtkowiak (TomekW)
Warning: date(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Friday, 10 October 2014, 12:27 GMT+2
Reason for closing: Fixed
Warning: date(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): 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. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Friday, 10 October 2014, 12:27 GMT+2
Reason for closing: Fixed
Could you explain me a step necessary to reproduce this error. Maybe we talk about another date field?