Project Planner for OSX - OSX version of Project Planner and Project Planner HD
FS#161 - Task Entry
Attached to Project:
Project Planner for OSX
Opened by William Motley (Billmotley21) - 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, 02 January 2015, 20:52 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 Monday, 27 July 2015, 14:34 GMT+2
Opened by William Motley (Billmotley21) - 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, 02 January 2015, 20:52 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 Monday, 27 July 2015, 14:34 GMT+2
|
DetailsWhen I enter a task both the start calendar and the end calendar shows open to make a selection. Also the closure icon is missing for once the task is created
|
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 Monday, 27 July 2015, 14:34 GMT+2
Reason for closing: Fixed
Additional comments about closing: Fixed in version 1.6.0
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 Monday, 27 July 2015, 14:34 GMT+2
Reason for closing: Fixed
Additional comments about closing: Fixed in version 1.6.0