• Resolved hirngesicht

    (@hirngesicht)


    Hello! Our staging site and our local test site are getting absolutely bombarded with this message. Any chance you could add a check of some sort?
    Maybe only log it once every x hours, or if you check WP_ENVIRONMENT_TYPE and only log it if it’s set to “production”?

    Everything still works as expected so this is a visual error only. A really annoying visual error since it fills the entire log, essentially hiding all other errors.

    From debug.log:

    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token
    [04-Dec-2025 12:17:08 UTC] [WP STATISTICS] [ERROR]: Failed to decrypt token

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Mehmet

    (@gandomi)

    Hello @hirngesicht,
    Thank you for reporting this issue and for providing the log details.

    The message “Failed to decrypt token” is only logged when WP_DEBUG is enabled, because the logging function in WP Statistics writes errors to debug.log exclusively under this condition.
    That means the behavior you are seeing is expected while WP_DEBUG is set to true, especially on staging or local environments.

    To stop these repeated entries from flooding your logs, you can simply disable debugging:

    define('WP_DEBUG', false);

    or, if you prefer to keep debugging enabled but prevent log file flooding:

    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', false);

    Everything in the plugin continues to work normally, this is only a visual/logging issue, not a functional error.

    If you would like to request improvements such as throttling the log messages or limiting them to production environments, you can submit feature suggestions here:

    https://feedback.veronalabs.com/boards/wp-statistics

    We appreciate your feedback and are always open to improving the plugin!

    Best regards,
    Mehmet

    Thread Starter hirngesicht

    (@hirngesicht)

    Thanks for the quick repsonse!

    The problem is that it’s not feasible to turn off WP_DEBUG on staging or testing since we are using those to test new features, etc.

    I’ll submit a feature suggestion, thanks!

    Plugin Support Mehmet

    (@gandomi)


    You’re very welcome, and thanks for the clarification.
    I understand that keeping WP_DEBUG enabled is essential for your staging and testing workflow. We’ll make sure your suggestion is reviewed, because adding a throttle or environment check would definitely help reduce unnecessary noise in the logs.
    Best regards,

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

You must be logged in to reply to this topic.