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

Plugin not working anymore (Bedrock + Sage 10)

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.

Hi,

On a website I've been working on for a few weeks, the plugin stopped working suddenly, and I can't find why...

I tried to switch theme (used Storefront for testing), disabled all other plugins but Husky and Woocommerce, but nothing works.

The plugin doesn't display anymore on the frontend.
The shortcodes seem to not work anymore neither.

The admin panel in Woocommerce > Product filters seem to work fine.

But when trying to edit its configuration in my sidebar (in the widgets), it's completely broken...
I get a red error message at the top"The"woof_widget" block has been affected by errors and may not function properly. Check the developer tools for more details."

When checking in the JS console, I see those errors :

I dont' see any other errors in the PHP logs...
I'm out of options, I don't know what to do...

Little precision : we're using Roots' Bedrock version of Wordpress, and their Sage 10 starter theme, maybe this has anything to do with this ?

Thank you for any help you'll be able to provide...

Hello

Could you give me the plugin version number you are using?

 

Yes, using the last version : 3.3.6.

Hello

Please paste your license key here - https://share.pluginus.net/image/i20230222134241.png -> https://share.pluginus.net/image/i20230222134511.png and  wp-admin access - https://share.pluginus.net/image/i20230222134615.png - I will check it

 

I have set a staging version up, I gave you all the necessary credentials in the topic private datas.

Hello

Looks like you disabled widget blocks (use legacy widgets) and now I can't check the error. And I think you did it with custom code that's why I can't turn it off

Thanks a lot for giving me the good email address for this account on my other topic ! I tried a few on our @rectangle.net domain, but didn't think about trying the Gmail account.
I don't know where this account comes from, I think a colleague of mine created it in 2021 since you said it's from this year, but I don't know why I was logged in on this one when I created this topic...
Anyway, that's not the subject !
(You can delete my other topic, it's useless to anyone).

Sorry, I forgot to mention that : the widget blocks disabling is managed by the"Disable Bloat for WordPress & WooCommerce" plugin.
I disabled the plugin, the widget blocks are back, and you can re-enable the plugin if you want to test things with the legacy widgets.

The Husky filters don't display on the frontend, with blocks widgets or with legacy widgets, none of the 2 works.
But with legacy widgets, I don't get errors in the widget settings, that's why I switched.

My  test - https://share.pluginus.net/image/i20240703134741.png and https://share.pluginus.net/image/i20240703135148.png

I can see the widget and edit it without any errors.

Oh... Yeah, I can see that... I don't understand, it doesn't work on the production website, but it works on the staging one, even when I rsync the files and copy the database from the production server...
I'm pretty lost here.

You know what ? I'll give you an access to the production website so that you can check the problem out directly.
I made a complete save just in case, but please be careful when using the admin to not break things up.

I put the credentials for the production server in the private note of the topic.

Hello

Ok! Please try to install and set up this plugin - https://wordpress.org/plugins/error-log-monitor/  - and check if there are any errors in the log

Hello,

I found the problem... Well not exactly, but I know what it was related to.

I'm using a plugin to avoid loading Wordpress plugins on the pages where they are not used.
This is the plugin I'm using : https://fr.wordpress.org/plugins/plugin-organizer/

Of course, I tried to disable it when debugging the problem with Husky, but I didn't notice something : the MU plugin installed by Plugin Organizer isn't removed when we disable the plugin, so it kept having an effect even with the plugin disabled.

But I don't know what happened : the Husky plugin worked correctly before, with Plugin Organizer enabled and used to execute Husky only on shop pages.
I removed the mu-plugin, check that Husky worked (and it did), then re-created the mu-plugin and re-enabled Plugin Organizer, and Husky still works correctly.
So I'm not sure what was the problem...

Maybe I should use the provided way to do this directly in the plugin options ? And not disable Husky with Plugin Organizer ?
I learnt about this option in Husky after I set Plugin Organizer up...
I'm not sure I understand how this option works (I got the FR translation, but it's not clean at all, a lot of options are hard to understand in french), can I use"https://at4.com/categorie-produit/*" to enable Husky on all product category pages ?
Edit: it doesn't seem to work that way, and I don't understand the french example to use link masks, it says :
Exemple de masque de lien: catégorie de produit.

I also have a second problem, but maybe you'd prefer that I make a new topic for this ?
I'm trying to use the dynamic hiding of empty terms, but it behaves strangely.

For instance, when reaching a category page for the first time, it seems to work fine.
If I select a filter, it still works.
But when I remove this filter, when the page reloads, all terms are displayed, even empty ones...

Hello

Yes, of course, it would be better to try to use our functionality. so that the filter works only on category pages: https://at4.com/categorie-produit/  OR /categorie-produit/

but maybe you'd prefer that I make a new topic for this ?  - Let's continue in this topic

Please try this option Advanced->Options - https://share.pluginus.net/image/i20240711000738.png  If no luck  could you try  - https://share.pluginus.net/image/i20240711000837.png