DataTables Warning when loading Bear Bulk Editor Page
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from LiamOz on June 4, 2023, 04:57Every time I load the BEAR Editor, I see this error message:
DataTables warning: table id=advanced-table - Ajax error. For more information about this error, please see http://datatables.net/tn/7
If I change the view count (amount of products), to let's say 50 or 100, it then throws this error:
DataTables warning: table id=advanced-table - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1
Images:
If I change the view to 5, 10, 15 products, the products load, though once I choose 20 items, it crashes.
The other day, I was able to view 50+ products, 100+ products. It leads me to believe that the BEAR Bulk Editor is crashing due to some invalid data within the product, perhaps? I'm not sure exactly... As it randomly stops working, I can't determine the reason for this.
After some investigation, and disabling plugins, it appears the issue lies with Redis Object Caching Pro - after disabling the Redis Object Cache, the issue is resolved.
I have not noticed any conflicts with any other plugins, which leads me to suggest that the BEAR Bulk Editor plugin is at fault for the issue, whether it be due to not grabbing the database items in accordance with standard WP coding practices, etc.
Is there a way I can further troubleshoot/diagnose the BEAR Editor, such as an error log dump, or stack trace, to see exactly where the error is coming from/what part of the code is failing?
I purchased my BEAR Bulk Editor plugin via CodeCanyon/Envato and have a license, if this info is required I can provide it.
Every time I load the BEAR Editor, I see this error message:
DataTables warning: table id=advanced-table - Ajax error. For more information about this error, please see http://datatables.net/tn/7
If I change the view count (amount of products), to let's say 50 or 100, it then throws this error:
DataTables warning: table id=advanced-table - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1
Images:


If I change the view to 5, 10, 15 products, the products load, though once I choose 20 items, it crashes.
The other day, I was able to view 50+ products, 100+ products. It leads me to believe that the BEAR Bulk Editor is crashing due to some invalid data within the product, perhaps? I'm not sure exactly... As it randomly stops working, I can't determine the reason for this.
After some investigation, and disabling plugins, it appears the issue lies with Redis Object Caching Pro - after disabling the Redis Object Cache, the issue is resolved.
I have not noticed any conflicts with any other plugins, which leads me to suggest that the BEAR Bulk Editor plugin is at fault for the issue, whether it be due to not grabbing the database items in accordance with standard WP coding practices, etc.
Is there a way I can further troubleshoot/diagnose the BEAR Editor, such as an error log dump, or stack trace, to see exactly where the error is coming from/what part of the code is failing?
I purchased my BEAR Bulk Editor plugin via CodeCanyon/Envato and have a license, if this info is required I can provide it.

Quote from LiamOz on June 4, 2023, 05:08I can confirm also, the WP_MEMORY_LIMIT is 2048M for our WP Instance.
The issue seems to be with Redis Object Cache Pro (Redis Object Caching), when I disable this plugin, I don't have any issues with the editor.
Kindly let me know how I can debug this issue.
I can confirm also, the WP_MEMORY_LIMIT is 2048M for our WP Instance.
The issue seems to be with Redis Object Cache Pro (Redis Object Caching), when I disable this plugin, I don't have any issues with the editor.
Kindly let me know how I can debug this issue.
Quote from Pablo Borysenco on June 5, 2023, 10:38Hello
Please paste your license key here - https://share.pluginus.net/image/i20230222134241.png -> https://share.pluginus.net/image/i20230222134511.png
To get error log you can use this tool - https://ewordpress.org/plugins/error-log-monitor/
If no luck - Please drop me wp-admin+FTP access - https://share.pluginus.net/image/i20230222134241.png ->https://share.pluginus.net/image/i20230222134615.png
Hello
Please paste your license key here - https://share.pluginus.net/image/i20230222134241.png -> https://share.pluginus.net/image/i20230222134511.png
To get error log you can use this tool - https://ewordpress.org/plugins/error-log-monitor/
If no luck - Please drop me wp-admin+FTP access - https://share.pluginus.net/image/i20230222134241.png ->https://share.pluginus.net/image/i20230222134615.png
Quote from LiamOz on June 5, 2023, 10:42Hi, I've added my purchase license key.
Can you confirm if the log tool you've provided will adequately follow stacktrace errors/follow the process by the BEAR Bulk Editor?
Also, can you confirm if this is the plugin? The link you sent doesn't work.
https://wordpress.org/plugins/error-log-monitor/
Hi, I've added my purchase license key.
Can you confirm if the log tool you've provided will adequately follow stacktrace errors/follow the process by the BEAR Bulk Editor?
Also, can you confirm if this is the plugin? The link you sent doesn't work.
Quote from Pablo Borysenco on June 5, 2023, 10:50This plugin logs all errors
Yes this is plugin from Wordpres.org You can search it - "Error Log Monitor"
This plugin logs all errors
Yes this is plugin from Wordpres.org You can search it -"Error Log Monitor"
Quote from LiamOz on June 6, 2023, 09:35Hi there, thanks for clarifying.
After further investigations, I can see here the following stack-trace: https://pastebin.com/ZLjEcqCt
I am uncertain as to how the issue is causing an out-of-memory exception, given that my WP Instance has a dedicated 8GB of RAM on a 32GB Server (PHP confirms 8GB RAM).
Upon further investigations, and chats with ChatGPT, it advised that the issue could likely be due to flushing the cache.
On
woocommerce-bulk-editor/index.php, line 516, there is the `wp_cache_flush();` code. It appears that this is the root cause of the issue.Commenting out the wp_cache_flush(); code removes the entire error stack completely. I do not believe this is an appropriate place for the cache flush to go.
Upon further inspection, the cache shouldn't be flushed within the foreach loop, it should be before the loop, as for example if you are loading 100, 200, 300, 400 even 500 products on the page (as I am), it would mean that it's flushing the cache up to 500 times!
The reason this isn't ideal is when using Redis Cache, for example, it is having to flush all caches associated to Wordpress, it is not reasonable or logical to place the cache flush within such foreach loops. Here's the revised code to index.php Ln: 512: https://pastebin.com/HQ2KRG3H
As you can see, I've commented the flush cache in the foreach loop, and moved it outside, just before the foreach loop is requested.
Please pass this feedback onto the developers, and let me know if this is a better way to logically handle the flushing of the WP cache.
Hi there, thanks for clarifying.
After further investigations, I can see here the following stack-trace: https://pastebin.com/ZLjEcqCt
I am uncertain as to how the issue is causing an out-of-memory exception, given that my WP Instance has a dedicated 8GB of RAM on a 32GB Server (PHP confirms 8GB RAM).
Upon further investigations, and chats with ChatGPT, it advised that the issue could likely be due to flushing the cache.
On woocommerce-bulk-editor/index.php, line 516, there is the `wp_cache_flush();` code. It appears that this is the root cause of the issue.
Commenting out the wp_cache_flush(); code removes the entire error stack completely. I do not believe this is an appropriate place for the cache flush to go.
Upon further inspection, the cache shouldn't be flushed within the foreach loop, it should be before the loop, as for example if you are loading 100, 200, 300, 400 even 500 products on the page (as I am), it would mean that it's flushing the cache up to 500 times!
The reason this isn't ideal is when using Redis Cache, for example, it is having to flush all caches associated to Wordpress, it is not reasonable or logical to place the cache flush within such foreach loops. Here's the revised code to index.php Ln: 512: https://pastebin.com/HQ2KRG3H
As you can see, I've commented the flush cache in the foreach loop, and moved it outside, just before the foreach loop is requested.
Please pass this feedback onto the developers, and let me know if this is a better way to logically handle the flushing of the WP cache.
Quote from Pablo Borysenco on June 6, 2023, 11:16Hello
Looks like this is the reason - https://share.pluginus.net/image/i20230606121104.png
Please try in file - \wp-content\plugins\woocommerce-bulk-editor\index.php - delete/comment this line - https://share.pluginus.net/image/i20230606121542.png - and do a test
Hello
Looks like this is the reason - https://share.pluginus.net/image/i20230606121104.png
Please try in file - \wp-content\plugins\woocommerce-bulk-editor\index.php - delete/comment this line - https://share.pluginus.net/image/i20230606121542.png - and do a test
Quote from LiamOz on June 6, 2023, 14:27Hi, did you read my message?
I already found the issue.
I am telling you the flush cache SHOULD NOT be in the foreach loop.
Please have your dev team move the cache flush out of the foreach loop. This is not necessary.
Hi, did you read my message?
I already found the issue.
I am telling you the flush cache SHOULD NOT be in the foreach loop.
Please have your dev team move the cache flush out of the foreach loop. This is not necessary.
Quote from Pablo Borysenco on June 7, 2023, 09:22Hello
Sorry, the answer was sent to me by the developer who checked the logs and he certainly did not read your message. It's my fault
I think the developers will fix it. Thank you!
Hello
Sorry, the answer was sent to me by the developer who checked the logs and he certainly did not read your message. It's my fault
I think the developers will fix it. Thank you!
Quote from LiamOz on June 7, 2023, 09:23No worries at all,
Can you confirm with the developers if they will fix this - I only ask as if not, then I need to keep note on my end to fix the code each time we update your plugin.
Cheers :)
No worries at all,
Can you confirm with the developers if they will fix this - I only ask as if not, then I need to keep note on my end to fix the code each time we update your plugin.
Cheers :)
Quote from Pablo Borysenco on June 7, 2023, 11:54Yes, I checked it, developer added this task to fix it
Yes, I checked it, developer added this task to fix it