Plugin does not save changes
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 baxuz011 on July 7, 2025, 22:51Hello,
I wanted to try your plugin, but unfortunately, it doesn't work for me.
I'm testing locally with "WordPress 6.8.1" and the "Woodmart" theme. I added your widget "HUSKY - Products Filter Professional for WooCommerce" to the "Shop page Widget Area".
The settings panel appears in the admin dashboard, but no matter which filter I try to modify, after clicking the "Save changes" button, all the changes are reset. In other words, no modifications are saved.
The filter does appear on the Shop page and offers two or three basic functions, but I can't customize anything.
I’m not sure what the problem could be, and I’ve run out of ideas on what else to try.
Best regards,
Dusan B.
Hello,
I wanted to try your plugin, but unfortunately, it doesn't work for me.
I'm testing locally with"WordPress 6.8.1" and the"Woodmart" theme. I added your widget "HUSKY - Products Filter Professional for WooCommerce" to the "Shop page Widget Area".
The settings panel appears in the admin dashboard, but no matter which filter I try to modify, after clicking the "Save changes" button, all the changes are reset. In other words, no modifications are saved.
The filter does appear on the Shop page and offers two or three basic functions, but I can't customize anything.
I’m not sure what the problem could be, and I’ve run out of ideas on what else to try.
Best regards,
Dusan B.
Quote from Pablo Borysenco on July 8, 2025, 11:20Hello Dusan
What plugin version number are you using?
Hello Dusan
What plugin version number are you using?
Quote from baxuz011 on July 8, 2025, 14:10Hello,
Thank you for your response.
I'm currently using the free version of your plugin, HUSKY – Products Filter Professional for WooCommerce, version 1.3.7.1, which I installed directly from the WordPress plugin repository.
I originally suggested this plugin to a client for their store — potentially even the premium version if everything worked well — but unfortunately, I haven't been able to get it to function properly in my tests.
Also, in the browser console, I can see that admin-ajax.php returns status 200, but the JSON response looks like this:
{"header":[{"value":"Title","width":"45%","editable":1,"key":"title","action":"woof_sd_change_title"},{"value":"Type","width":"45%","key":"type"},{"value":"Actions","width":"10%"}],"rows":[]}
I'm not sure if this is expected behavior, but I wanted to mention it just in case it helps identify the issue.
Would using an older version of the plugin possibly resolve the issue? If there's anything else I can provide to help troubleshoot the problem, please let me know — I'm happy to assist.
Hello,
Thank you for your response.
I'm currently using the free version of your plugin, HUSKY – Products Filter Professional for WooCommerce, version 1.3.7.1, which I installed directly from the WordPress plugin repository.
I originally suggested this plugin to a client for their store — potentially even the premium version if everything worked well — but unfortunately, I haven't been able to get it to function properly in my tests.
Also, in the browser console, I can see that admin-ajax.php returns status 200, but the JSON response looks like this:
{"header":[{"value":"Title","width":"45%","editable":1,"key":"title","action":"woof_sd_change_title"},{"value":"Type","width":"45%","key":"type"},{"value":"Actions","width":"10%"}],"rows":[]}
I'm not sure if this is expected behavior, but I wanted to mention it just in case it helps identify the issue.
Would using an older version of the plugin possibly resolve the issue? If there's anything else I can provide to help troubleshoot the problem, please let me know — I'm happy to assist.
Quote from Pablo Borysenco on July 9, 2025, 11:05Hello Dusan
Sometimes this behavior can be on local servers, it is related to the settings of the local environment.
I recommend trying this tool - https://localwp.com/ - for local development and testing the plugin on it.
Hello Dusan
Sometimes this behavior can be on local servers, it is related to the settings of the local environment.
I recommend trying this tool - https://localwp.com/ - for local development and testing the plugin on it.