• Resolved d1nwp

    (@d1nwp)


    Hi, the plugin seems not to respect the localtime set on the system as well as the one set in php.ini by date.timezone =. The logging timestamp in the logs is UTC though CET is the that of the system. Because of that I have an issue with fail2ban recognizing and blocking failed logins. At the moment I am doing a “hacky” workaround and set date_default_timezone_set('CET'); manually in the log.php but would be interested in a general solution.

    • This topic was modified 1 month ago by d1nwp.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Blobfolio

    (@blobfolio)

    WordPress itself actually resets PHP’s default time zone to UTC early into setup to make it easier to construct “local” times using the stored site preference (a timezone string or offset or nothing).

    Jeepers Peepers has been using UTC rather than site time for consistency, especially across multiple sites and servers, but you make a good point.

    To that end, I just pushed a new release (0.5.4) with support for an extra config override, BLOBAUDIT_LOG_UTC, that can be used to toggle between the two choices.

    Once you’ve updated, double-check your site’s timezone is set to the desired locale (Settings > General), then add the following to wp-config.php:

    // Use site time instead of UTC for Jeepers Peepers logs.
    define('BLOBAUDIT_LOG_UTC', false);

    Log times should reflect the current site time rather than UTC thereafter.

    Thread Starter d1nwp

    (@d1nwp)

    Thank you so much, works like a charm ??

    best regards

    • This reply was modified 1 month ago by d1nwp.
Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.