PluginUs.Net - Business Tools for WooCommerce and WordPress

[realize your idea - make your dreams come true]

Support Forum

You need to log-in to create request (topic) to the support

Fatal Error When Trying to Filter by Brand.

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 please
If 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.
12

Hello,

I’m encountering a fatal error on my site related to memory exhaustion, which I believe is tied to the WooCommerce Products Filter plugin. Below is the error message I’m receiving:

[17-Mar-2025 16:38:37 UTC] PHP Fatal error: Allowed memory size of 8589934592 bytes exhausted (tried to allocate 2124352 bytes) in /home/*****/*****/public_html/wp-content/plugins/woocommerce-products-filter/ext/front_builder/classes/options-sections.php on line 94

Steps to reproduce the issue...

Go to the applications Page.

https://jamisonh66.sg-host.com/application/

Select a Product Equipment Make

We choose Caterpillar as it's a common one...

This shows the Error / Error 502, which gets logged to debug.log

Many thanks in advance for any help you can offer.

I have been in touch with my hosting team regarding this and they have directed me to seek help from the plugin developers.

Hello

Please add  ftp+wp-admin  access - https://share.pluginus.net/image/i20230222134241.png ->https://share.pluginus.net/image/i20230222134615.png - I will  check it

Hi Pablo,

Thanks, I have added WP Login info and FTP access.

Hope this is something that can be fixed. Thank you for looking into this.

Hi Pablo,

I hope you're doing well.

Can you please confirm if you're currently investigating the issue with the plugin? We’re now seeing a different error on the category and Shop pages.
This error is an addition to the error reported previously.

I wasn’t sure if you're already troubleshooting this, but either way, I wanted to share these error messages with you in case they help.

Please let me know your thoughts and what you find.

Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given
in /public_html/wp-content/plugins/woocommerce-products-filter/ext/front_builder/classes/options-sections.php:48

Hello

Please do a test

Hi Pablo,

The second issue above has been fixed, however the first issue at the start of this thread still seems to be present, where the plugin Fatal Errors when trying to filter by brand - example CATERPILLAR, from the Applications page.

https://jamisonh66.sg-host.com/application/

https://jamisonh66.sg-host.com/application/?swoof8=1&pa_equipment-make=caterpillar

Hope this makes sense. Please let me know what you think.

 

 

Hello

I don't get this error. Please  clear all cache and do a test

Hi Pablo,

The error gets logged as a fatal error, even after clearing all caches and testing this again.

Either by selecting the brand manually from this applications page...

https://jamisonh66.sg-host.com/application/

or by going direct and including the brand query in the URL to the same page - this causes the fatal error to be logged.

https://jamisonh66.sg-host.com/application/?swoof8=1&pa_equipment-make=caterpillar

So either selecting the brand from the left-hand side of the"Search by Application" page  - or infact going directly to"Caterpillar" on the Applications page, seems to cause the site to crash.

Please help.

 

Hello

Ok!  Try  now please

Hi,

Problem is still the same.

https://jamisonh66.sg-host.com/application/

Application page works fine, - the filter loads  - but selecting a MAKE - for example Caterpillar, results in the website/page crashing, once Caterpillar or any other make to be selected.
The crash causes the  fatal errors to be logged by/from the Husky plugin to the WordPress debug log.

Please help

Example Screenshot

Hello

Please drop me a text of the errors

Hi,

I initially thought the issue was resolved, but I’m now seeing the shortcodes for the filters appear in the sidebar—however, the filters themselves are not displaying.

The Husky plugin is enabled, as I suspected the issue might have been due to it being turned off. Could you take a look and let me know what might be causing this?

Just to confirm, currently, the shortcodes for the filters are visible in the sidebar, but the actual filters are not showing up.

Hello

In Advanced->Options - clear this field - https://share.pluginus.net/image/i20250324130834.png   - I disabled it temporarily for testing.

Hi,

The errors are below. I spoke to the hosting team, and they advised against arbitrarily increasing memory limits, as this doesn't address the underlying issue.

[26-Mar-2025 10:10:34 UTC] PHP Fatal error: Allowed memory size of 8589934592 bytes exhausted (tried to allocate 2124352 bytes) in /home/customer/www/public_html/wp-content/plugins/woocommerce-products-filter/ext/front_builder/classes/options-sections.php on line 94

Could you please check if the filter is handling large product lists efficiently, or if the way it processes part number, type, and engine model selections is causing unnecessary strain? This issue seems to occur when selecting a Product Equipment Make (for example, Caterpillar, DAF, or JCB).

Please let me know what you find. Thank you!

 

Hello

The display of the filter does not depend on the number of products, it depends more on the number of elements (attributes and categories)

As I wrote above, I disabled this module - https://share.pluginus.net/image/i20250326123750.png , so this error should not occur.

Hi,

Thanks for your response. I understand that the display of the filter depends more on the number of attributes and categories. However, the issue still seems to occur when selecting a Product Equipment Make (like Caterpillar, DAF, or JCB), which could involve a large number of attributes in the background.

Could you please confirm if there are any optimisations or adjustments that can be made to reduce the strain on the system when dealing with these specific selections?

I had to re-enable the filter on the front end, following your instructions, and that’s when I was able to re-create the error.

If these issues can be resolved, we’ll be ready to launch the website.

Thanks again for your help!

 

That's the whole problem, to fix something we need to find the cause.  I disabled this module before and you still said that the error exists - https://share.pluginus.net/image/i20250326130427.png

And at the moment I can't find any pattern, after all my changes you always see an error, although I don't see it even in the logs

 

Hi Pablo,

I need to clarify that the error doesn’t occur when you disabled the module. However, I also wasn't able to use the filter when the module was disabled.

With the module enabled, I experience the issue when navigating from"Shop ALL" to"Search by Application" and then choosing a Product Make (any Product Make, though Caterpillar is typically chosen as it’s a popular make) from the left-hand side Product Make dropdown. The site then returns an Error 500.

I can see the error by navigating to wp-content and downloading the debug.log. I want to stress that the error only occurs on that page when filtering by Product Make.

Could you please advise on the next steps to help identify the cause of the issue? I understand you’ve tried some changes already, but I’m still encountering the error and would appreciate any further guidance.

Thanks for your help!

Hello

Please do the test.  Just check everything and if the error repeats immediately give me the error text  - https://jamisonh66.sg-host.com/application/?swoof8=1&pa_equipment-make=caterpillar

 

 

 

Thank you Pablo. that works for me! Could you kindly explain what has been done to fix this issue as we have another"staging" site of the same website and I'd like to carry the changes over to that site too.

12