Strict Standards error

  • rsix08

    (@rsix08)


    12 years, 8 months ago

    Does anyone what this is related to or know how to fix this error. The plugin I am using bookingwiz is producing it . I have also opened a ticket on the support forum.

    Strict Standards: date_default_timezone_get(): 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 ‘America/New_York’ for ‘EDT/-4.0/DST’ instead in /homepages/7/d485992227/htdocs/wordpress/booking/includes/config.php on line 45

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/7/d485992227/htdocs/wordpress/booking/includes/config.php:45) in /homepages/7/d485992227/htdocs/wordpress/booking/admin.php on line 59

Viewing 4 replies - 1 through 4 (of 4 total)
  • Clayton James

    (@claytonjames)

    12 years, 8 months ago

    Looks like that’s a commercial plugin. I don’t find a free version available that can be tested. While I suspect it might be related to the time zone configuration in php.ini on your server (Example: date.timezone = America/New_York), you may need to wait for a response from support at Convergine for an accurate answer.

    Scriptrunner (Doug Sparling)

    (@scriptrunner)

    12 years, 8 months ago

    Are you running in DEBUG mode and running PHP 5.4 or greater?

    As of PHP 5.4, E_STRICT has been included as part of E_ALL, so if you’re running in DEBUG mode, you’ll now see Strict Standards warnings (note – they’re warnings, not errors), where you didn’t see them before in PHP 5.3.x or earlier.

    Thread Starter rsix08

    (@rsix08)

    12 years, 7 months ago

    Thanks was able to get it going with global php to 5.3 on my site. still looking into if it can run on 5.4

    Scriptrunner (Doug Sparling)

    (@scriptrunner)

    12 years, 7 months ago

    It should work fine with PHP 5.4, as Strict Standards are only warnings (but ones the plug author should probably take note of). These warnings should only display (with PHP 5.4) if you have WP_DEBUG set to true. As I said, it wasn’t until PHP 5.4 that E_STRICT was added to E_ALL (which WordPress uses for wP_DEBUG), and that’s why you’re seeing it now in PHP 5.4. Basically the output is just saying there’s a better or safer way to do something even though the code is syntactically correct.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Strict Standards error’ is closed to new replies.