Jetpack crm creating many errors in my debug.log

  • impulsivia

    (@impulsivia)


    1 week, 5 days ago

    Hi, the Jetpack CRM plugin is triggering a huge amount of errors in the debug.log. What is going on?

    [30-May-2026 13:51:38 UTC] PHP Deprecated: Safe\ibase_modify_user(): Implicitly marking parameter $last_name as nullable is deprecated, the explicit nullable type must be used instead in .../wp-content/plugins/zero-bs-crm/vendor/thecodingmachine/safe/generated/ibase.php on line 406
    [30-May-2026 13:51:38 UTC] PHP Deprecated: Safe\ibase_pconnect(): Implicitly marking parameter $database as nullable is deprecated, the explicit nullable type must be used instead in .../wp-content/plugins/zero-bs-crm/vendor/thecodingmachine/safe/generated/ibase.php on line 483

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

Viewing 1 replies (of 1 total)
  • Plugin Support Stef (a11n)

    (@erania-pinnera)

    1 week, 1 day ago

    Hello @impulsivia,

    Thanks for sharing the PHP errors. What you’re seeing are PHP “deprecated” notices, not fatal errors. They seem to be coming from a third-party library included in Jetpack CRM (thecodingmachine/safe) and are related to newer PHP versions (PHP 8.1+). Essentially, PHP is warning that a certain coding style used in that library is outdated and will be removed in the future.

    The important point is that these notices do not indicate a problem with Jetpack CRM’s functionality. The plugin should continue working normally. They’re simply being written to the debug log because debugging is enabled on your site.

    These notices are quite common when the site is running newer PHP versions (8.1, 8.2, 8.3), andWP_DEBUG / WP_DEBUG_LOG is turned on.

    If this is a production site as it looks like, you may want to disable debug logging to prevent the log file from filling up with non-critical notices.

    Let me know how you get on!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.