Hi, great plugin, I use it on every WordPress installation I have, but I have 2 small comments:
1. When I use the command error_log(print_r($request->get_params(), true)); to display the contents of Array(), instead only Array ( appears in the log without any further part, however the log file itself contains all the necessary information
2. The plugin does not remember the setting of the number of displayed results per page, after reloading the browser it always defaults back to 10

I am experiencing an issue where your plugin is not detecting a nonce-related error on my website. Initially, I encountered the following warning in the logs:

csharp

Copia codice

[20-Sep-2024 06:41:43 UTC] WARNING: [pool www.publicmusic.it] child 202 said into stderr: "Chiave "nonce" non trovata nell'array."

This suggests that a nonce key was missing from the array. However, after disabling the “Transposh Translation Filter” plugin, the error changed to a JavaScript error:

csharp

Copia codice

[20-Sep-2024 06:29:03 UTC] JavaScript Error: Uncaught ReferenceError: mejs is not defined in https://www.publicmusic.it/wp-includes/js/mediaelement/mediaelement-migrate.min.js?ver=6.6.2 on line 1.

It appears that the original nonce error is not being detected or logged correctly by the Debug Log Manager plugin. Could you offer any guidance on improving nonce error detection, or suggest how to address these issues?

Thank you for your assistance!

Hello,

I love using Debug Log Manager, it’s helping me a lot to debug websites, so thanks a bunch for that first of all!

What I would like is to have more information about errors, like for example with the free plugin Fatal Error Notify, we have the Error level, the message, the file, the line, but especially what I would love for DLM to have is the request, the referrer and User ID if we have it.

Like so:
Error Level: E_ERROR
Message: Uncaught Error: Call to undefined function […]
File: […]
Line: 26
Request: /wp-admin/admin-ajax.php?action=[…]
Referrer: […]
User ID: 5

Thanks for letting me know if it’s possible to add this in Debug Log Manager.

With this plugin installed I get 404 messages about non found fonts:

/wp-admin/fonts/Inter-Bold.woff
/wp-admin/fonts/Inter-Regular.woff2
/wp-admin/fonts/Inter-Bold.woff2

Doing a grep with these fonts in the source tree gave hits in \wp-content\plugins\debug-log-config-tool\dist\wpdebuglog-admin.js.

What can be done (apart from uninstaling your great plugin) to get rid of those 404s?

Just to let you know that this plugins trunk branch on the SVN is empty, which causes weird problems when trying to include this plugin as part of @wp-env and other dev environments.

See this issue – https://github.com/WordPress/gutenberg/issues/57512

I have reproduced the same issue today and then found the above thread.

Including the trunk URL made my .wp-env.json script fail:

    "plugins": [
       "https://downloads.www.ads-software.com/plugin/debug-log-manager.zip",
        "."
    ],

with failure:

? Response code 404 (Not Found)
HTTPError: Response code 404 (Not Found)
    at Request._onResponseBase (/Users/xxx/.asdf/installs/nodejs/20.16.0/lib/node_modules/@wordpress/env/node_modules/got/dist/source/core/index.js:913:31)
    at Request._onResponse (/Users/xxx/.asdf/installs/nodejs/20.16.0/lib/node_modules/@wordpress/env/node_modules/got/dist/source/core/index.js:948:24)
    at ClientRequest.<anonymous> (/Users/xxx/.asdf/installs/nodejs/20.16.0/lib/node_modules/@wordpress/env/node_modules/got/dist/source/core/index.js:962:23)
    at Object.onceWrapper (node:events:634:26)
    at ClientRequest.emit (node:events:531:35)
    at origin.emit (/Users/xxx/.asdf/installs/nodejs/20.16.0/lib/node_modules/@wordpress/env/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)
    at HTTPParser.parserOnIncomingClient (node:_http_client:698:27)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
    at TLSSocket.socketOnData (node:_http_client:540:22)
    at TLSSocket.emit (node:events:519:28) {
  code: 'ERR_NON_2XX_3XX_RESPONSE',

the workaround is to specify a version

"plugins": [
       "https://downloads.www.ads-software.com/plugin/debug-log-manager.2.3.3.zip",
        "."
    ],

After installing I got several rows of notifications in the plugin settings screen, among others:

Warning: Undefined variable $kiloBytes in …/public_html/wp-content/plugins/system-dashboard/admin/class-system-dashboard-admin.php on line 1328

Warning: Undefined variable $kiloBytes in …/public_html/wp-content/plugins/system-dashboard/admin/class-system-dashboard-admin.php on line 1328

Warning: Undefined variable $kiloBytes in …/public_html/wp-content/plugins/system-dashboard/admin/class-system-dashboard-admin.php on line 1328
Skip to main contentSkip to toolbar

• This topic was modified 3 months, 4 weeks ago by nudnavda.

On a WP site running PHP 8.2, Query Monitor alerts me of the following persistent issue with WP Debug Log:

Warning: foreach() argument must be of type array|object, null given

The location is:

wp-content/plugins/debug-log-manager/classes/class-debug-log.php:682

The complete trace is as follows:
wp-content/plugins/debug-log-manager/classes/class-debug-log.php:682
DLM\Classes\Debug_Log->get_entries_datatable()
wp-content/plugins/debug-log-manager/bootstrap.php:266
Debug_Log_Manager->create_main_page()
wp-includes/class-wp-hook.php:324
do_action('tools_page_debug-log-manager')
wp-admin/admin.php:259

I don’t require assistance for this, just reporting it in order to fix compatibility with PHP 8.2+

I got a critical error when trying to access the WP Admin dashboard.

Upon checking the logs, It showed me the following error:-

WordPress version 6.5.3
Active theme: PopularFX (version 1.2.5)
Current plugin: Debug Log Manager (version 2.3.3)
PHP version 8.2.18
Error Details
=============
An error of type E_ERROR was caused in line 342 of the file /home/tandukar/public_html/wp-content/plugins/debug-log-manager/classes/class-debug-log.php. Error message: Out of memory (allocated 993734656 bytes) (tried to allocate 777831904 bytes)

I had to delete the debug log file which was 389 MB to fix this issue.

Please add an option for the debug log to get automatically cleared after the file reaches X size specified by the user.

recently I’ve noticed many resource usage spikes on my site, and I installed your plugin in an attempt to pin down the specifics. But sadly my site crashes whenever I toggle the error logging to OFF. Requiring a reinstall of an OLD wp-config file to restore my site.

I realise that it is most likely caused by the underlying issue I’m wrestling with and NOT your plugin. But could you guess what is going on from the error message?

Fatal error: Uncaught Error: Undefined constant “WP_DEBUG” in /home/mysite/wp-config.php:49 Stack trace: #0 /home/public_html/mysite/wp-load.php(50): require_once() #1 /home/public_html/wp-blog-header.php(13): require_once(‘/home/pub…’) #2 /home/public_html/index.php(17): require(‘/home/pub…’) #3 {main} thrown in /home/public_html/mysite/wp-config.php on line 49

I’d love to get your plugin working as I think it will help me.

thank you

Excellent plugin, however, it would be really great if it had the ability to filter a little more. For example, 99% of my log is information that some function in the plugin is deprecated, which is completely meaningless to me, because I have no influence on the code of other authors’ plugins.

On the other hand, when building a new theme, I would like to see all other errors and warnings, because the information about deprecated functions in PHP is displayed to me on the fly by VSCode.

At the moment I can only view them one at a time, which is cumbersome because you have to keep switching between different filtering options.

• This topic was modified 7 months, 1 week ago by wellmadeonline.

Hello,

Is the plugin supposed to change settings to avoid this warning? I want to see the warnings within the dashboard without displaying them elsewhere. https://prnt.sc/Neg4ihtDjQAj

Thanks

This plugin has been closed as of March 7, 2024 and is not available for download. This closure is temporary, pending a full review.

Is there a way to sideload it in the meanwhile?

I installed the plugin for the first time a couple months back on a project I was working on and was impressed by how well it worked, but every site I’ve installed it on since it just sits there and says there’s nothing in the log, which has me perplexed and a bit disappointed, as I spend a *lot* of time in the WP Debug logs.

Using the most reccent site as an example, I set up the plugin to diagnose an issue with a recent site migration where a plugin is causing the theme to crash on the front end. It read that error logging was turned off, so I flipped the switch to turn it on and proceeded to reproduce the error; nothing happened.

Wondering if I needed to activate WP_DEBUG manually, I added the following to wp-config.php:

define('WP_DEBUG', TRUE);           // Turns on error tracking
define('WP_DEBUG_DISPLAY', FALSE);  // Suppresses displaying errors on site
define('WP_DEBUG_LOG', TRUE);       // Records errors in /wp-content/debug.log (unless other location specified)

Which created the debug.log file and added an entry with the fatal error shown in the code block below:

[04-Mar-2024 10:25:02 UTC] PHP Fatal error:  Uncaught LogicException: The template folder "theme" was not found. in wp-content/plugins/age-gate/vendor/league/plates/src/Template/Folders.php:60
Stack trace:
#0 wp-content/plugins/age-gate/vendor/league/plates/src/Template/Name.php(111): League\Plates\Template\Folders->get('theme')
#1 wp-content/plugins/age-gate/vendor/league/plates/src/Template/Name.php(83): League\Plates\Template\Name->setFolder('theme')
#2 wp-content/plugins/age-gate/vendor/league/plates/src/Template/Name.php(45): League\Plates\Template\Name->setName('theme::partials...')
#3 wp-content/plugins/age-gate/vendor/league/plates/src/Template/Template.php(83): League\Plates\Template\Name->__construct(Object(League\Plates\Engine), 'theme::partials...')
#4 wp-content/plugins/age-gate/vendor/league/plates/src/Engine.php(291): League\Plates\Template\Template->__con in wp-content/plugins/age-gate/vendor/league/plates/src/Template/Folders.php on line 60

The error does not show up in the plugin, however.

Is there some critical setup step that I’m missing? I *really* want to use this plugin to assist with these sorts of tasks.

• This topic was modified 8 months, 3 weeks ago by bigcloudmedia.

It would be helpful to have a duplicate “Clear log” button at the top of the page to avoid having to scroll to the bottom to clear the log file.

I don’t know if this plugin is installed correctly and had to disable it when a fatal error was triggered. The basics would be nice to know if the error was my fault or not.

I’m having the same issue Jesse (@jeswd) had here: Stops working when path to wordpress app changes

In my case, the error was triggered when cloning a site in Local by Flywheel: the plugin keeps looking for the path that matches the site it was originally activated on.
Deactivating or uninstalling doesn’t solve this.
I also witnessed the same problem when migrating a local site to live, or staging site to production.

I was able to locate and delete the relevant key in phpMyAdmin (debug_log_manager_file_path) and then dereactivated the plugin, which works, but obviously isn’t ideal.

My proposed fix would be to re-determine the path each time the plugin is activated, just like it does on first activation.
Unless I’m missing something, it seems like it could be a satisfactory fix, and wouldn’t require much work to be implemented?

• This topic was modified 9 months, 3 weeks ago by jrmyfranck. Reason: typos, clarification

Hi,

I’ve been using your great plugin now on a couple of my sites. Its been very helpful so far – especially when combined with Variable Inspector Pro :)??

Basically as the title states, I would like to know, if its possible to disable JavaScript error logging, while keeping PHP error logging enabled?

The reason behind my question is the following scenario which I encountered:
In one of my sites I had a faulty JavaScript ResizeObserver, which was creating JS errors like crazy (literally dozens per second)…
The client side code of Debug Log Manager now tried to log the JS error into the backend log via ajax, each time it occured. After a few seconds the whole website was down for everyone, as the website was basically DDOSing itself…

At the moment this is the only reason that prevents me from using this plugin on a production site. (Of course I fixed my mistake, but potentially this could happen again…)

I guess, the easiest workaround for this would be to simply disable JS error logging once a website is live.

Is this possible at the moment? If not, could you please add a setting for this?

(Maybe you could also add some sort of request debouncing or only make an ajax error logging request if the new JS error is not exactly the same as the last one logged?)

Thanks ??

• This topic was modified 11 months, 2 weeks ago by gorebatschov.

Hi dear support,
when I go to the tab “logs” it does not show me anymore the logs but it only shows: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Can you help?

So I was working on a plugin and I tried to test it, when I pressed activated it says: Plugin could not be activated because it triggered a?fatal error. And this plugin shows and ! green icon that you got an error I click it to see what is the error and I see nothing, I tired manually to download the .log life and it is empty.

Hi,

Nice plugin. Helps a lot for debugging.

As for the wp-config, this plugin adds several rules such as

define( 'DUP_SECURE_KEY', );
define( 'SCRIPT_DEBUG', true );
define( 'WP_DEBUG_LOG', '' );
define( 'WP_DEBUG_DISPLAY', false );
define( 'DISALLOW_FILE_EDIT', true );

After disabling/deleting the plugin, these rules are not automatically removed. I found this because the “DISALLOW_FILE_EDIT” prevents one of my PHP from firing.

My question is:

1. Should the plugin auto-remove these added rules after disabling the plugin? If it should, why is it not removed in my case?
2. If the rules added by the debugger are not removed after disabling/removing the plugin, where should I check manually for the rules so I can remove them myself to prevent future conflicts?

Thanks

When viewing log on an iPad all of the characters in each column are displayed in a single character column. There appears to be plenty of space to the right but all of the text is left aligned with a single character on each line.

Hello,

I’m really enjoying your plugin, but I’ve encountered a small issue. Many plugins use prefixes like [DEBUG], [INFO], [WARNING], and [ERROR] when debugging is activated. However, these specific messages are being replaced by “No error message specified…”, which requires me to manually access the file to view them. I believe this problem stems from the way timestamps are processed, as the plugin isn’t anticipating a second set of square brackets.

To address this, I’ve added a line in the file /debug-log-manager/classes/class-debug-log.php within the get_processed_entries() function:

// Read the errors log file 
$log 	= file_get_contents($debug_log_file_path);

// NEW: Ignore words between square brackets
$log = preg_replace("/\[([a-zA-Z]+)\]/", "$1", $log);

I hope this suggestion proves helpful for future updates.

Best regards,

Hi,

After we installed and activated your plugin, we started to have some NEW and STRANGE errors logged. I always enable debug after a major change, like WordPress 6.2 or 6.3, or PHP upgrade (8.1.x). We do have always some notices, deprecated mostly. But those are new and strange and probably do not come from the plugins. And TWO sites have the same issues.

Take a look at the errors logged (examples):

JavaScriptUncaught TypeError: Cannot read properties of undefined (reading 'setLocaleData') in

Uncaught TypeError: e(...).autocomplete is not a function in https:// removed /wp-includes/js/jquery/jquery.min.js?ver=3.7.0 on line 2 column 28722 at https:// removed /blog/

JavaScriptSyntaxError: “” literal not terminated before end of script in https: // re mo ved /wp-content/plugins/wpdiscuz/assets/js/wpdiscuz-combo.min.js?ver=7.6.3 on line 10 column 17066 at …

Those errors are not shown ANYWHERE in my f12 console, never, and never had them.

Now, removing (for now) your plugin, and leave debug log on, there are NO issues like those.

I think your plugin is doing that for some reason?

Thanks

Urgent: please check why the text is shown in vertical direction, as it was reported weeks ago.

Necessary: please add an option to expand the actual message because the table doesn′t show the actual log information, just part of it.

Useful: please add the link to the log file, not only the truncated path. That way the log file could be directly accessible, instead copy/pasting the path, etc. And add some format, if possible, to that log information.

Hi,

Is there anyway to select what Debug directives we want active? For example “scripts” debug is heavy and not needed in most cases.

Thanks

My technical language is English. The owner prefers another default language for his site. Is there a way ( with or without this plug-in) to have debug messages (on screen or in debug.log) appear always in my preferred language?

Hi,

Firstly, this is a really useful plugin. Thanks for your great work here.

I have an issue where I have moved my WordPress installation to another server, and the path to the application has changed.
The old path was /home/894978.cloudwaysapps.com/xdszkbgszd/public_html/
And the new path is /home/1042953.cloudwaysapps.com/xdszkbgszd/public_html/

Even after the removal of the WP_DEBUG_LOG line in wp-config created by the plugin, switching debug logging on and off, and uninstalling and reinstalling the plugin, it still creates in wp-config:
define( ‘WP_DEBUG_LOG’, ‘/home/894978.cloudwaysapps.com/xdszkbgszd/public_html/wp-content/uploads/debug-log-manager/fedgroupcomau_202306212318_debug.log’ );

Assuming there is an entry in the DB saving the path, and it doesn’t get wiped ever. Would be great to have a button or something to refresh the path, or even just have this refreshed on plugin deactivation.

Thanks!

Hi ! Great plugin !
Is it possible to not display for example PHP notices ?
I know that there is a dropdown to see the type of errors I want, but it could be great if it was possible to choose what must be displayed in the list.
If I just want warnings and fatals, I have to select the first one in the dropdown, then the other one :/
A great improvement would be a list with checkboxes and I only select what I wanna see, and it remembers my choice.
And it could be a little visual improvement if in the whole list thre was a color to identify notices, for example a red left border on fatal, orange on warning, etc.
Thanks !

Two tables is overlapping.
https://share.ulement.com/z8ub4XRP

Love this plug-in it helped me fix an issue with my website. But only with some issues. I have to resize the screen to see the log. I’m on safari and wp 6.2.