I’ve fixed the Show Count issue, so disabling it now correctly hides the counts and the setting is properly saved. This fix will be included in the upcoming update.
I also managed to find and reproduce the contextual count issue you reported, you can see the incorrect behaviour in the first screenshot below.
I’ve corrected the filtering/count logic and have been testing it with different combinations of filters. So far, everything seems to be calculating and updating correctly, as shown in the screenshot below.
I’m going to run some additional tests before publishing the update, just to make sure everything is working as expected. If it is, the update will be live by tonight / tomorrow.
Once it’s live, please let me know if you still encounter any issues on your setup, especially anything I may not have been able to reproduce during my testing.
Once the update is live, ‘ll mark this support topic as resolved. But I’ve also noted all your feature requests. I really like some of the ideas you suggested, and they’ll be the next things I look into after this bug-fix update.
Thank you again for taking the time to report everything in such detail, it really helped me track down the issue!
First of all, thank you so much for the kind words, the detailed feedback, and all the suggestions! 🙂
Regarding the Show Count option, that definitely shouldn’t behave like that. I’ll look into it right away and get it fixed asap.
For the incorrect AJAX counts, unfortunately I haven’t been able to reproduce the issue on my testing site yet. I actually ran into something similar during development and managed to fix it at the time, or so I thought, so I’ll do some further testing to figure out where the issue is still occurring and get to the bottom of it.
I’ll focus on fixing these bugs first and getting an update out. After that, I’ll definitely add your feature suggestions to the roadmap and look into them as the next step of development. Those were actually very interesting ideas!
Thanks again for the feedback and for taking the time to report all of this. It helps me improve the plugin, and I’m really glad to hear it’s been useful to you!
I’ve changed the plugin so that Google Fonts are now disabled by default and can be enabled if the user wants to use them. When they’re disabled, the plugin simply inherits your website’s typography instead.
The update has been published and should be available to download within the next few hours.
Thank you again for bringing this to my attention. Feedback like this really helps improve the plugin. If you have any other suggestions or run into anything else, please don’t hesitate to let me know!
Thank you very much for your kind words! I’m really glad to hear you’re enjoying the plugin so far. 😊
You are absolutely right about the fonts. The plugin was originally built as a personal project for my own use, and I later decided to publish it because I thought it might help others too, especially after struggling with WooCommerce filter plugins for years.
When I added Google Fonts to allow deeper customization, I completely overlooked the fact that I was still forcing Manrope and Sora as the default fonts. My mistake!
I’ll work on this right away, and as soon as I’ve finished testing everything, I’ll publish an update.
Thank you again for taking the time to report this, and I hope you’ll continue to enjoy using the plugin!
