Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php on line 14

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_misc.php on line 1621
tag_error <txp:posted format="%a" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%I:%M%p" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%I:%M%p" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%I:%M%p" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%a" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%I:%M%p" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%I:%M%p" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%I:%M%p" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%a" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%I:%M%p" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%I:%M%p" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%I:%M%p" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%a" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%I:%M%p" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%I:%M%p" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%I:%M%p" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%a" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%I:%M%p" /> ->  : getdate(): 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 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%I:%M%p" /> ->  : mktime(): 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 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%I:%M%p" /> ->  : 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 'CET/1,0/no DST' instead  on line 1177

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/publish.php on line 477
Puntada sin Hilo: Página 2

Ir al contenido

jue
sep
10

2009

¿Qué me falta en Android?

Android

Hace aproximadamente dos meses y medio me hice con un terminal móvil con el sistema operativo Android, en concreto, con un HTC Magic. Desde hacía 5 años, no había tenido un teléfono que no utilizara Symbian, así que, el cambio ha sido bastante brusco. Entre otras cosas, decidí abandonar Symbian porque, en estos tiempos 2.0, donde los terminales táctiles y la conectividad a tiempo completo empiezan a mandar, se estaba quedando bastante atrás: al igual que Windows Mobile, no da la sensación de adaptarse tan rápidamente como lo han hecho los iPhone, las BlackBerry o Android.

La verdad es que el cambio ha sido indudablemente para mejor (y eso que no tenía ningún tipo de queja con mi antiguo N95), Android, desde mi punto de vista, tiene un montón de virtudes que le van hacer estar en lo más alto en un corto plazo de tiempo. No sólo por la empresa que lo empuja, sino también por su mentalidad abierta y la comunidad de usuarios y desarrolladores que crece a su alrededor.

De todas formas, sin esforzarse mucho se pueden encontrar docenas de páginas y artículos destripando las bondades y las virtudes de este sistema operativo, así que, en este caso, voy a centrarme en las faltas que le encuentro y las cosas que, desde mi punto de vista, deberían mejorarse:

... [continuar leyendo ¿Qué me falta en Android?]

mié
jul
29

2009

Un poco más "2.0"

Como díría el gran sabio Enjuto: "follower, follower, twitter, twitter, twiiter, twitter, twitter, follower, follower, follower, twitter, follower, twitter..."

En mi afán de llegar siempre un poco más allá en esto de la web 2.0, me he apuntado a la moda del microblogging y me he registrado en Twitter. He de reconocer que, en un primer momento, todo este tema del "¿Qué estás haciendo?" me parecía una tontería bastante grande, pero, la verdad, es que una vez que empiezas tiene su aquel.

¿Qué puedo hacer con twitter que no pueda hacer con, por ejemplo, los estados en Facebook?... pues nada. ¿Qué puedo hacer en twitter que no pueda hacer de manera fácil en este blog?... pues nada. Pero entonces, ¿por qué me registro?... pues porque es 2.0, y lo usa Armstrong y... yo que sé, pues porque soy así.

En fin, que con motivo de este update sobre mi persona, he procedido a hacer lo mismo en el blog, por lo que, desde ya, podréis ver mis últimos tweets en la columna derecha de esta página. Dado que es mucho más sencillo actualizar twitter que el blog, supongo que será la parte que más se mueva de esta web. Espero que os guste esta nueva faceta.

mar
jul
21

2009

Organizando una boda...

Dos meses ya sin actividad en el blog y con la de cosas que tengo que contar. Durante este tiempo se me han juntado muchas cosas sobre las que escribir: me he casado, he estado por Egipto, voy a cambiar de coche, me he vuelto a caer de la moto... total, un sinfín de historias para llenar líneas y líneas.

En fin, intentaré ponerme al día en un periodo corto de tiempo, aunque con el verano por el medio, no se sabe. Voy a empezar por recomendar un par de lugares indispensables para organizar un boda original, aunque sólo sea porque se lo han ganado por el buen trato que nos han dado:

  • Restaurante Peña Mea de San Cucao: Un lugar ideal para casarse. Ofician bodas civiles debajo de una panera, gente muy maja y comprometida y, sin duda, bastante bien de precio. Ofrecen una originalidad y un nivel de dedidacación dignos de admirar. Y, para rematar, te ceden la panera para pasar la noche de bodas... de todos los lugares que miramos, este no tiene rival.
  • Chupitum: A través de su página web, http://www.chupitum.com, venden originales detalles para los invitados de una boda. Vasos de chupito, copas y botellas con el nombre de los novios y personalizados para cada uno de los invitados. A cada invitado se le puede asignar un personaje de los cientos que tienen o, si no te gusta ninguno, pedir uno nuevo hecho a medida. Todas las copas son dibujadas a mano... una verdadera obra de arte. Si buscas originalidad, acertarás.

jue
may
28

2009

La gran final...

Por fin había llegado el día más importante del concurso... la final. Habíamos llegado tres parejas hasta aquí, y ninguna estaba dispuesta a regalar nada. Sólo teníamos que volver a hacer la misma coreografía del otro día, a poder ser, mejor que el fin de semana anterior... y luego a esperar la decisión del jurado.

Después de empezar con muchísimo retraso y hacerse bastante de rogar, por fin estaba todo hecho. Cuando salimos al escenario a escuchar la decisión del jurado y ver que no éramos ni los terceros ni los segundos, creo que nuestra cara cambió por completo: lo habíamos conseguido, ¡habíamos ganado!. Tanto trabajo había dado sus frutos.

Aquí dejo el vídeo de nuestra actuación... la misma que el fin de semana anterior con sutiles mejoras:

Aquí cuelgo también el vídeo de los segundos clasificados... desde mi punto de vista una gran coreografía y un más que merecido puesto (lo siento, pero el vídeo de los terceros clasificados no lo tengo). La canción es "Con los pobres estoy" de Roberto Roena:

En conclusión, la experiencia ha sido buena y no me arrepiento de haberme presentado, pero, si hubiera una segunda edición, me lo pensaría mucho antes de volver a repetir. La organización del concurso ha sido bastante mala (por no decir que fue un cachondeo): retrasos poco justificados, horas de ensayo perdidas por falta de organización, premios bastante pobres y distintos de lo acordado... y un montón de cosas más que deberían cambiar para que todo vaya bien la próxima vez. Lo mejor de todo, la gente, los participantes y la salsa.

lun
may
18

2009

Segundo día de concurso en el casino

Bueno, este sábado llegó la hora de presentar la coreografía para el concurso del casino, nuestra pequeña creación. Ana y yo escogimos la canción "Tiroteo" del New Swing Sextet... corta y con muchos golpes, ideal para coreografiar. Es la primera vez que preparamos una coreografía y, la verdad, es que salimos muy contentos. No será ni la mejor coreografía del mundo, ni la más original, pero, al menos, es nuestra, así que ilusión no nos fataba.

Sólo tres parejas pasarían a la final del sábado que viene y, por suerte, nosotros fuimos una de ellas. Ahora, viendo el vídeo, me doy cuenta de que la cosa se podía haber mejorado bastante (sobre todo por mi parte), así que tendremos que esforzarnos un poco más para la próxima vez.

Gracias de nuevo a todas las voceras y voceros que estuvisteis allí dejándoos la garganta para animarnos. Espero que el sábado que viene tengáias más razones aún para chillar.