WordPress.org

31. randell
    Member
    Posted 2 years ago #

    You can do what you like (as I'm sure you know) but this us a PHP 5.3.0 issue and not a WordPress issue.

    Actually, it's both, since WordPress is using PHP and is affected by its changes.

    Yes, I agree that we can do what we like, but in this case it would only mean fixing the problem every time a WordPress installation breaks when PHP is upgraded *pointing to the original problem*.

    Why not?

    Again, it risks breaking (or at least messing up) existing WordPress installations when PHP is upgraded by someone who is not aware that doing so needs modifying of the date.timezone directive. Placing the date_default_timezone_set() function on the core makes WordPress installations more sturdy. When I say putting it in the core, I mean making it available for the next release without us having to modify our WP installations anymore.

32. ultrawebsites
    Member
    Posted 2 years ago #

    Strangely, I'm administering a website hosted in Europe which needs to be on Vancouver Canada time, and using php.ini with the date.timezone setting recently stopped working (haven't had time to nail down why), yet adding the setting in functions.php now makes the timezone correct again. FYI, putting it functions.php seems far preferable to me to putting it in wp-config.php, as it avoids adding non-standard settings/lines to core WordPress files, and thus helps avoid it being overwritten in future.
    Matt

33. Rev. Voodoo
    Volunteer Moderator
    Posted 2 years ago #

    putting it functions.php seems far preferable to me to putting it in wp-config.php, as it avoids adding non-standard settings/lines to core WordPress files,

    wp-config.php is not over-written in an upgrade....

Topic Closed

This topic has been closed to new replies.