Timezone database is corrupt

  • nettim

    (@nettim)


    4 years ago

    Fatal error: date_create(): Timezone database is corrupt – this should *never* happen! in … /wp-includes/functions.php on line 5691

    The web site is managed by Virtualmin on CentOS 7 with PHP 7.4.12.
    The WordPress version is 5.5.3.
    The Web PHP Engine is FPM.

    Another web site on the same Virtualmin uses the same version of WordPress, PHP, PHP Engine, …, but working properly without any issues.

    The line 5691 is:
    $datetime_object = date_create();

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator t-p

    (@t-p)

    See info in this thread points in the right direction:
    https://stackoverflow.com/questions/8751221/php-timezone-database-is-corrupt-error

    Thread Starter nettim

    (@nettim)

    Hi t-p,

    Thanks for replying. The suggested post mentioned several root causes. I need to figure it out one by one.

    At this moment, I have stupid questions. How do I identify which php.ini has referenced by the web site that I have got trouble?

    Thread Starter nettim

    (@nettim)

    Hi t-p,

    All of the stuff mentioned on given web page are doesn’t help on my case. The problem is still exist. The latest error message is:

    Warning: timezone_open(): Unknown or bad timezone (Asia/Tokyo) in ....../wp-includes/functions.php on line 5690

Warning: date_create(): Invalid date.timezone value 'Asia/Singapore', we selected the timezone 'UTC' for now. in ....../wp-includes/functions.php on line 5691

Fatal error: date_create(): Timezone database is corrupt - this should *never* happen! in ....../wp-includes/functions.php on line 5691
    Thread Starter nettim

    (@nettim)

    Additional information. I haven’t follow the “function mysql2date( $dateformatstring, $mysqlstring, $translate = true )” changing part. I don’t know how to and where to change the mentioned coding to add the false return code.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Timezone database is corrupt’ is closed to new replies.