cron job and date errors
Hi Ben,
I'm loving how simple Sendy is the setup and use but I'm having a couple of problems.
Installation was fine, SES setup went fine. It just when I go to send out a small campaign that I'm having an issue.
I'm on a cPanel VPS, my cron is: php /home/domain/public_html/sendy/scheduled.php >/dev/null 2>&1
If I look at http://my_domain/sendy/scheduled.php is see a bunch of these even though my timezone is setup:
[25-Nov-2012 02:36:43 UTC] PHP Warning: date() [function.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 'Australia/Melbourne' for 'EST/11.0/DST' instead in /home/domain/public_html/sendy/includes/helpers/class.amazonses.php on line 51
I hope you can help.
Regards
Marty
I'm loving how simple Sendy is the setup and use but I'm having a couple of problems.
Installation was fine, SES setup went fine. It just when I go to send out a small campaign that I'm having an issue.
I'm on a cPanel VPS, my cron is: php /home/domain/public_html/sendy/scheduled.php >/dev/null 2>&1
If I look at http://my_domain/sendy/scheduled.php is see a bunch of these even though my timezone is setup:
[25-Nov-2012 02:36:43 UTC] PHP Warning: date() [function.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 'Australia/Melbourne' for 'EST/11.0/DST' instead in /home/domain/public_html/sendy/includes/helpers/class.amazonses.php on line 51
I hope you can help.
Regards
Marty
This discussion has been closed.
Comments
This is a warning and does not affect any functions (though I'll remove it in the next update).
So it's not an issue with Sendy or your server. Have you verified both your email and domain?
And are you using your AWS security credentials from here https://portal.aws.amazon.com/gp/aws/securityCredentials ?