Debug.log Errors – WP and/or PHP Plugin Compatibility?

    • # il y a 2 jours et 16 heures

      Hi @Matias, or anybody else that can provide some help.

      I wonder what is the status of the WPCustomerArea plugin? It has not been updated in a long time and I am afraid there are more and more errors that are being generated in debug.log file (in the wp-content folder on server).

      I have wrote about this issue several weeks ago, but nobody responded. So, I am wondering if anybody else has similar error messages being generated in the debug.log file and if there is any update on these issues related to WP Customer Area?

      I still don’t know if these errors are related to the latest WP versions and/or PHP version, because I am constantly getting debug.log flooded with these warning messages:

      [26-Oct-2025 19:52:14 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cuar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tahoce47/public_html/wp-includes/functions.php on line 6121
      [26-Oct-2025 19:52:14 UTC] PHP Deprecated: Creation of dynamic property CUAR_NotificationsAdminInterface::$no_addon is deprecated in /home/tahoce47/public_html/wp-content/plugins/customer-area-notifications/src/php/helpers/notifications-admin-interface.class.php on line 22

      There are about 50 of these messages EVERY MINUTE, so debug.log file in wp-content folder quickly becomes larger, and the size of the file about 12MB in one day!!! I believe this also slows down website loading times, so I would really appreciate if you could help me fix this. Please let me know if I should provide you with any other information, because this must be solved. We are using latest WordPress v6.8.3 and still using PHP v8.2 (but would like to update to v8.3 when it’s safe!).

      Please reply ASAP. Thanks!

    • Matias Larralde
      Maître des clés
      # il y a 1 jour et 22 heures

      Hi Danijel,

      Sorry for the late reply. Our team is currently working on an update to address these compatibility issues. We’ll notify you as soon as it’s available.

      In the meantime, if the debug.log file size is causing server issues, you can temporarily disable WordPress debugging by setting WP_DEBUG to false in your wp-config.php file (if it’s not critical for your workflow).

      Thank you for your patience,

      The WP CustomerArea Team

Vous lisez 1 fil de discussion

You must be logged in to reply to this topic.