Project Planner HD is iPad version of Project Planner
FS#69 - Text In Task Goes Outside Preset Box
Attached to Project:
Project Planner HD
Opened by Robert Toscano (Rjtoscano) - 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 Saturday, 16 April 2011, 16:05 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, 31 October 2011, 10:21 GMT+2
Opened by Robert Toscano (Rjtoscano) - 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 Saturday, 16 April 2011, 16:05 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, 31 October 2011, 10:21 GMT+2
|
DetailsWhen exporting project into PDF the text inputted goes outside the pre-determined boxes and doesn't automatically adjust the cells to accept. I will forward an example to the support email address.
|
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, 31 October 2011, 10:21 GMT+2
Reason for closing: Fixed
Additional comments about closing: Fixed in version 1.3.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, 31 October 2011, 10:21 GMT+2
Reason for closing: Fixed
Additional comments about closing: Fixed in version 1.3.0