Plugin Author
Bowo
(@qriouslad)
There’s no KB article at the moment as the setup should be self-explanatory. Can you copy paste the error message you saw?
LOL, I may be the one that breaks the mold. The error message is below, wp-config is set to ‘WP_MEMORY_LIMIT’, ‘256M’. Does your plugin require that much memory? The next limit increase is 512M but your plugin memory size in the error surpasses it.
WordPress version 6.4.3
Active theme: Storefront Child (version 1.0) Current plugin: Debug Log Manager (version 2.3.1) PHP version 8.0.30
Error Details
=============
An error of type E_ERROR was caused in line 338 of the file /var/www/wp-content/plugins/debug-log-manager/classes/class-debug-log.php. Error message: Allowed memory size of 536870912 bytes exhausted (tried to allocate 233441800 bytes)
-
This reply was modified 2 years, 3 months ago by
kingbrown75. Reason: proofreading
Plugin Author
Bowo
(@qriouslad)
Please check the size of your debug log file. Looks like it may have grown too large?
Thanks, looks like the file size is 288.27MB but with no way to reduce it except manually, log ratation or installing another plugin to do one task (not optimal). Perhaps this is a feature to add to your plugin since it created a crash report and give more value to your plugin. Just a recommendation, no offense intended.
I don’t know how to manually reduce the log, rotation appears like creating a new log without the old infomation your plugin needs to read and really don’t want to install another plugin with 67 already installed. Do you have any suggestions on manually reducing the log if adding the feature is not in your interest?
-
This reply was modified 2 years, 3 months ago by
kingbrown75.
Plugin Author
Bowo
(@qriouslad)
I’ve been thinking of ways to automate purging the size of the log file, probably in a Pro version of the plugin though.
If you want to do it manually, look up the file in the wp-content/uploads/debug-log-manager/ folder, download it to your computer, delete error messages that are older. I have never actually tried to open a 200MB+ log file, so, hope that works.
The other solution is to simply delete that file on the server to start fresh.
The memory was increased to 640M and worked, I didn’t wan’t to loose log info for current issues. Thanks for your help
-
This reply was modified 2 years, 3 months ago by
kingbrown75.