Hi everyone,

We’ve been working on Optiontics, a WooCommerce product options plugin built for stores where normal variations quickly become difficult to manage.

The idea came from seeing product setups that needed much more than just size and color, things like:

• Custom text and engraving
• Conditional product options
• Dynamic and formula-based pricing
• Custom measurements
• Build-your-own bundles
• Personalized apparel and gifts
• 25+ field types

Optiontics provides a visual, no-code way to build these configurations directly for WooCommerce products.

We also built an AI Assistant into the workflow. It is not just there to generate text. You can describe the type of product you are selling, and it helps create the actual product-option setup that you can continue editing and refining.

We launched Optiontics on Product Hunt today, and we’d really value feedback from WooCommerce developers, store owners, and other WordPress plugin users.

Product Hunt:
https://www.producthunt.com/products/optiontics

For Product Hunt users, we also have 18% off any plan with coupon code PH18OFF.

I’d especially love to hear:

What’s the most complicated product customization you’ve had to build in WooCommerce?

TLDR:

Install this plugin and WordPress admin will be fully translated into whatever language you are using:

https://wordpress.org/plugins/superdav-ai-language-packs/

I noticed many customers using Loco translate + AI to translate my plugin and other plugins on their site which were missing translations for the plugin strings. Also I wanted to provide translations for my plugin for all users no matter how many people used their language. The WordPress org plugin repository does not allow AI generated transactions to be submitted through the official translate.wordpress.org site, for good reason.

So I built Superdav AI language packs to provide a service that would translate plug-ins with high quality models and a solid system prompt and provide the translations for the whole community. So just by installing this plugin all of WordPress admin can be 100% translated into any locale.

So if your WordPress installation is not set to English please try this plugin and let me know how well it works for you.

Hello!

I have a contact page that appears hidden, at first...

When you go on the website, and click "Contact" the form is there, but it's "missing".
You can only see if it you drag your mouse across the page and then everything appears.

It's only when you refresh the page that the form loads properly. (see pics below)

Anybody else have this issue? Or know how to fix it?

Was digging through the WordPress AI team notes from August and found this, and I'm surprised it hasn't gotten more attention.

They're working on something called a trust ladder. Four levels of autonomy for an AI agent, plus a zero level that works as a kill switch. It behaves roughly like user roles, subscriber up through administrator, except what's getting the role isn't a person. The way it's proposed, each ability declares what trust level it needs, you set your own threshold on your site, and anything above your threshold doesn't even register with the agent. It just isn't there as far as the agent is concerned.

What got me was the reasoning. The notes say they discussed treating agents as a new type of user rather than something separate, "partly because that's the direction regulation seems to be heading." So part of why your AI plugin might end up with a role is legal, not technical.

Full disclosure before anyone asks, I build an AI content plugin, so I have a horse in this race. But the thing I keep chewing on cuts against my own category.

Core is solving permission. I don't think permission was ever the hard part. An agent sitting at the top of that ladder with full admin trust and no verified sources will still publish confident, fluent, completely invented articles, and it'll have permission for every one of them. Trust level tells you what an agent is allowed to touch. It says nothing about whether what it wrote is true.

Genuinely curious where people land on this. If you had the slider today, where would you set it? And is there any level of autonomy you'd hand an agent on a site you actually make money from?

Source is the WordPress AI team blog, August 6 summary, if you want to read it yourself: https://make.wordpress.org/ai/

Disclosure up front: it's my plugin, and there's a link to my own write-up at

the bottom. Everything worth knowing is in this post, so you don't need to

click it.

Since March, WordPress.org rotates eight lesser-known plugins into the Featured

tab — the one that opens by default under Plugins → Add New. No application,

no fee, someone there picks eight every two weeks.

The curator published figures for the first cohort in March and said more would

follow. There hasn't been a second report, and as far as I can find no featured

author has ever written up what it did to them. So I logged mine.

Public numbers, all checkable on any plugin page:

- Active installs: 30 → 200

- Downloads: about 1,300 over the run

- Ratings: 1 → 2

- Support threads: 5 → 7

My own instrumentation, same 13 days on either side:

- Activations: 26 → 565 (2.0/day → 43.5/day)

- Completed the setup wizard: 96% → 79%

- Created an account: 54% → 12%

- Ever ran a search: 50% → 4.8%

22× more people, one tenth the engagement. In absolute terms: 13 people used

the thing in the 13 days before, 27 during.

Not bots — email verification held at the same rate on both sides (13 of 17

before, 100 of 132 during). Real people, different reason for arriving.

One thing I haven't seen documented anywhere: the order of the eight is redrawn

every single day. Same eight plugins for all 13 days, different sequence each

time I looked. Days I was 1st or 2nd averaged 89 activations, days 3rd to 8th

about 35. That's only 2 days in the top band, and one of them was day 2 of the

rotation, so novelty and position are tangled. Observation, not a result.

Full write-up with the daily roster of all eight plugins and the caveats:

https://queryra.com/blog/wordpress-org-featured-plugin

Anyone else been through a cohort? I've got one plugin's worth of data and

would like to compare.

As the headline say, i am selling mine etchwp license with ACSS. Both have unlimited sites and the etch license is the one from the very begining before we knew anything. PM for price

I just added a new feature to my plugin, and the cool thing about this is that it finds pages you are already ranking for in Google, and then alerts you if you don't have any internal links pointing to them. This is probably a really good way to boost a couple of pages that are already ranking with very little effort and time.

The plugin is called SEO Medic. There is a free version, as well as a paid version with some AI features where you can use your own API key and things like that.

Anyhow, I thought this would be helpful for people who are still on WordPress, like I am.

One thing I always found annoying with WordPress video player plugins is that switching players often means updating old posts one by one.

If a site already has hundreds or thousands of videos, replacing every video with a new shortcode isn't practical.

That's why I built Entronn Player.

It can automatically enhance existing supported videos across your WordPress site, so there's no need to edit old posts or migrate content manually. The original content stays untouched.

Current features include:

• MP4 support
• HLS / .m3u8 support
• Automatic replacement of existing videos
• Resume playback
• Subtitles
• Poster images
• Shortcodes for manual embeds
• Pre-roll, mid-roll and post-roll ads
• Skippable and non-skippable ads
• Custom player appearance

The idea is simple: install it and give your existing videos a better player without rebuilding your content library.

It's a new plugin, so I'd genuinely appreciate feedback from anyone managing a video-heavy WordPress site.

Check out Entronn Player on WordPress.org

​

I recently launched \*\*StayNexus Hotel Manager\*\*, a free and open-source hotel management plugin for WordPress.

I started building it because I noticed that many WordPress hotel solutions mainly focus on taking bookings, while running a hotel involves much more than that.

A hotel needs to manage rooms, availability, guests, reservations, payments, billing, staff, and bookings coming from different channels.

So I wanted to build a complete hotel management system that works directly inside WordPress.

Some of the things StayNexus currently includes:

\* Room types and room management

\* Availability management

\* Guest management

\* Booking management

\* Online payments with Stripe

\* Manual/offline payments

\* Pay-at-hotel bookings

\* Hotel billing

\* Staff management

\* Frontend room search and booking

\* Channel-manager integration for OTA synchronization

The OTA integration is particularly interesting to me because hotels often have to manage bookings from their own website as well as platforms such as Booking Dot com and other OTAs.

The plugin is completely free and open source, and I'm still actively developing it.

I'd really like to hear from people who run hotels, manage hotel websites, or develop WordPress solutions for hotels.

\*\*If you were building a hotel management system today, what feature would you consider essential that existing solutions often get wrong or don't provide?\*\*

I'm looking for honest feedback — especially things that could make StayNexus more useful in a real hotel environment.

I realized photos on my blog are not optimized and takes up way too much space. I understand Wordpress scales images and my photos are never rendered in its original state. I'm fine with the scaling, but I'm wasting server space.

I'm looking for a plugin that optimizes all photos stored in the media gallery and then deletes the originals. I've found plugins that does this, but they all seem overkill and I'm not sure which one to use.

I'm willing to pay, but don't need a subscription, since I'm only going to use it once for approx 500 photos. Which plugin would you suggest?

Webhook registration. Subscription logic. Stripe plan IDs wired to a settings page. Admin token controls. Freemium gating.

Every single plugin. Same scaffolding. Every single time.

I was building an AI-powered form plugin for WordPress and hit that wall again around day two. The actual product - the conversational lead qualifier, the live preview builder, the lead dashboard - took maybe 30% of my time. The other 70% was infrastructure I'd already written three times before.

So I built the scaffolding into the platform itself. AI Forms WordPress auto-registers webhooks, handles the Razorpay and Stripe subscription flow, and gives admins a token management panel out of the box. You open the builder, configure your questions and qualifying criteria, set your brand color, drop the embed on any WordPress page, and you're done.

No backend setup. No custom webhook endpoints. No copy-pasting payment logic from a previous project.

I'm wondering how common this is - do other WordPress developers just accept the boilerplate tax, or have you found a way to actually eliminate it? What's your current workflow when you're spinning up a new plugin from scratch?

Using WordPress admin on my phone always felt more awkward than it should. So I’ve been working on a different experience with my plugin, OpenStation.

I recorded a demo on my iPhone showing WordPress running as an installable PWA, with an app-like home screen, full-screen admin windows, and an app switcher to jump back into what you were doing.

You can open tools, minimize them, restore them, and write posts, all within the same interface. For me, it feels much smoother than using the usual WordPress admin in a mobile browser.

To clarify: it’s a Progressive Web App that you add to your home screen, rather than a native App Store app.

🎥 Watch the mobile demo

What’s the most frustrating part of managing WordPress from your phone? I’d love feedback on whether this would improve your workflow.

I've been building WordPress sites for clients for years. The same problem keeps showing up: contact forms collect garbage leads. Someone fills in a name and email, hits submit, and you have no idea if they're a real buyer or someone who clicked the wrong tab.

So I built AI Forms WordPress. Instead of a static form, it runs a short AI conversation - asks qualifying questions, scores the lead, and logs the full transcript to a dashboard. The client sees qualified: true or qualified: false on every lead. No more cold outreach to tire kickers.

What surprised me was the backend side. I didn't want to write webhook logic and subscription handling from scratch again. So I made the plugin builder handle all of that automatically - Stripe integration, webhook registration, the whole freemium-to-Pro upgrade path. You drop it into a WordPress site and it just works.

262 visits in the first 30 days. One paying user so far. Early, but the signal is there.

I'm curious - for those of you building client sites or internal tools on WordPress, how are you currently handling lead qualification? Static forms, third-party integrations, something custom? Would genuinely like to know what's working.

Hey everyone!

Quick context: A while ago, I built SVisciano – Light-Dark Theme Mode because my personal website was originally built with a dark theme, and almost every dark-mode plugin on WordPress assumed a light base design and forced rigid, hardcoded styles.

I wanted something completely theme-agnostic that relies on native CSS variable mapping: you define your base theme (Light or Dark), scan your page CSS variables, and map them to build the secondary mode (Light-to-Dark or Dark-to-Light).

I just published v0.3.0 with some key quality-of-life updates that make color mapping much more flexible:

• CSS Variable Overrides: You can now map a color variable directly to another CSS variable (e.g. var(--my-accent)), instead of being forced to use raw hex/RGB strings.
• Alpha Channel Support: Updated color pickers to natively support RGBA opacity/transparency controls right from the WP admin panel.

Key highlights of how it works:

1. Zero external JS dependencies — performance-focused & lightweight.
2. Doesn't force predefined dark styles — you retain 100% control over client/brand colors.
3. Built-in scanner to quickly find CSS color variables on any page.
4. Includes Import/Export for easy migration between environments.

It's completely free on the WP repository

👉 WordPress Plugin: https://wordpress.org/plugins/svisciano-light-dark-theme-mode/

Would love to get your thoughts or feedback on how to improve the variable injection workflows further!

I’ve been working on a WooCommerce store where only certain products need an age restriction, and initially I thought this would be a pretty simple problem.

Something like:

But once you start thinking about the actual purchasing flow, it gets a lot messier.

For example:

• What happens if only one product category is age-restricted?
• What if someone lands directly on the restricted product URL?
• What happens when a restricted product is added to a cart that also contains normal products?
• Is a frontend popup enough, or should the cart/checkout also validate the restriction?
• Should a customer have to verify every time, or can the verification be remembered?
• Is a simple “I am 18+” checkbox sufficient, or should DOB verification be used?
• What happens with caching/CDNs?
• What about different minimum ages for different categories?

The part I found most interesting is that an age gate can look like it’s working perfectly while only protecting the frontend.

For a WooCommerce store, I think the more important question is:

Can the customer actually complete the purchase without satisfying the restriction?

That led me to approach it more as a WooCommerce access-control problem rather than just a popup.

I ended up building an age-restriction plugin for WooCommerce because I couldn't find the exact workflow I wanted. I'm the developer behind it, so full disclosure there.

The approach currently supports things like:

• DOB or simple age-confirmation verification
• Restrictions at site, product, category, tag, or page level
• Different minimum ages for different rules
• Cart/add-to-cart and checkout validation
• Remembering verification with signed cookies
• Optional external verification providers
• Customizing the verification modal

I also wrote up what I learned while working through the different scenarios here:

https://codersgrow.com/woocommerce-age-restriction-guide/

I'm particularly interested in how other WooCommerce developers handle this.

Do you treat age verification mainly as a frontend UX problem, or do you enforce it again at cart/checkout/server level?

And if you've implemented it before, what ended up being the annoying edge case you didn't think about initially?

AuditWand Accessibility went live on WordPress.org this week. I built it because every accessibility plugin I tried either locked the useful fixes behind a paid tier or injected a floating "accessibility widget" that changes nothing in the actual HTML. This one does neither: everything that runs on your own site is free, and nothing is added to your visitors' pages except the fixes you switch on.

**Why this matters, in practical terms**

About one in six people lives with a disability.

**Websites that don't take care of there accessibility concerns can get sued.**

On a typical WordPress site they hit walls the rest of us never notice:

- A screen reader hits an image with no alt text and says nothing, or reads out "IMG_4032.jpg".

- A link that only differs from the text by colour is invisible to someone who can't see that colour.

- A form field with only a placeholder has no name once you start typing in it, so a screen reader user doesn't know what it's for.

- Someone who can't use a mouse presses Tab and can't see where they are, or can't get past the menu at all.

- A phone user who needs to zoom can't, because the theme disabled pinch-zoom.

It's also now the law in most markets: the European Accessibility Act has applied to most businesses selling into the EU since June 2025, US web accessibility lawsuits run into the thousands every year, and Ontario's AODA applies to larger organisations. And the same fixes help everyone, including search engines, which read pages the way a screen reader does.

**What the free version does (no account, nothing leaves your site)**

*Check while you write*

- A "Check this page" button in the editor, drafts included. It runs 89 automated checks (the axe-core engine, the same one professional auditors use) and shows each problem next to your content with a plain-English explanation of what's wrong, who it affects, and how to fix it. 54 of the most common issues have explanations written specifically for WordPress users.

- 3 "worth reviewing" checks for things a machine can't decide alone: vague link text like "click here", images marked decorative that might not be, and text that may actually be an image.

- Optional automatic check on every save.

- Dismiss any finding with a recorded reason (kept in an Ignore Log you can reverse), and a "send to developer" handoff that copies a finding as a ready-to-paste ticket.

- History of your page checks on your own site.

*Fix in one click, all 16 free, each reversible and logged*

- Skip-to-content link for keyboard users

- Visible keyboard focus outline

- Underlined links in content (no colour-only links)

- "(opens in a new tab)" announced to screen readers

- Or stop content links opening new tabs at all

- A real label on the search field, and no empty searches

- A label on the comment box

- Page language and text direction declared, so screen readers use the right voice

- Pinch-zoom re-enabled on mobile

- Forced tab-order overrides removed

- Redundant title-attribute tooltips removed

- Fallback page titles for pages that have none

- Labels for form fields that only have a placeholder

- "(PDF, 1.2 MB)" appended to document links

- Block new PDF uploads (existing files untouched)

- An "Accessibility statement" link in the footer

These are server-side changes to the HTML your site sends. No front-end script, no overlay, nothing slowing the page.

*Audit your media*

- Media Library Audit: every image in your library with its alt-text status and where it's used, in one list. Edit alt text inline, mark decorative images in one click, filter to "missing alt text" and work through them in order. As far as I can tell nothing else does a whole-library alt text view.

*Show your work*

- A downloadable accessibility statement template.

- An "accessibility monitored" badge and a public status page where visitors can report a barrier.

**What the paid plans add (only things that need a server)**

Pro ($19/mo): scans every page of your live site in the cloud (500 pages per scan), monthly scheduled scans that run whether or not anyone opens WordPress, regression alerts by email that say what broke and where, full history with trends and scan-to-scan comparison, a hosted accessibility statement that updates itself from scan data, dated PDF reports mapped to EN 301 549 / EAA clauses, an accessibility column in your Posts and Pages lists, "view on page" with element screenshots, bulk review, weekly summaries. Business ($49/mo): the same across 5 sites, weekly scans, 2,000 pages per crawl, reports in English, German and French, 3 team seats.

Scan data is stored in the EU (Frankfurt), a DPA is included on every plan, and your site is verified before every scan so results always describe your site and not a stranger's.

**On "all 16 free"**

The most popular checker plugin in the directory ships 16 fixes too and keeps four behind its paid tier. I don't think the difference between free and paid should be which four fixes you're allowed, so all sixteen are free here. Paid is for the cloud work.

**What it will never claim**

That it makes your site "compliant". No automated tool can: automated checks find a subset of the barriers, and the rest need a person. It finds the mechanical problems, fixes the ones it can, and tells you what to do about the rest.

**Try it in your browser first**

The listing has a Live Preview button that spins up a WordPress site with the plugin installed, no download needed, about a minute:

- Free plugin (WordPress.org, with the Live Preview button): https://wordpress.org/plugins/auditwand-accessibility/

- What Pro and Business add, and pricing: https://auditwand.com/pricing

- Documentation, including a page for every issue and every fix: https://auditwand.com/docs

- Try a single page of any site, no install, no account: https://auditwand.com/scan

Disclosure: I'm the developer. Feedback welcome, especially anything confusing, missing, or wrong.

I just released a free Progressive Web App Plugin for WordPress. It turns any WordPress or WooCommerce site into an installable app, with offline browsing and push notifications, and you never pay a subscription fee for it.

Most push notification plugins work like this: you connect your site to their paid service, and once you cross a few thousand subscribers, you start paying every month just to message people who already opted in on your own site. Your subscriber list lives on their servers, not yours.

This one works differently. You create a free Firebase project yourself, paste in three values, and notifications go out from your own project. No subscriber cap, no per-message cost, no monthly bill. The list stays in your own database, and you can export or delete it whenever you want.

Key features in the free version:

• Installable app with your own icon, splash screen, and app window, no browser bar showing
• Offline browsing through a service worker, so a dropped connection does not end the visit
• Push notifications on Android, desktop, and iOS through your own Firebase project
• Auto-push when you publish a new post, plus a one-time welcome notification for new subscribers
• A dashboard with installs, subscribers, notifications sent, and a full delivery log
• Works with WooCommerce, AMP, multisite, and WPML

This is version 1.0, brand new, so I expect there is more to fix as real sites start using it.

If you run a WordPress or WooCommerce site, have you looked into turning it into an installable app before? Curious what stopped you: the setup, the ongoing cost of push notifications, or something else entirely.

Free version: https://wordpress.org/plugins/devdiggers-pwa/
Pro version: https://devdiggers.com/product/progressive-web-app-for-wordpress/

Hi everyone,

Full disclosure, I’m part of the team behind Pointics, a loyalty and rewards plugin built for WordPress.

We’re currently running our Early Bird Lifetime Deal, and I wanted to share a quick heads-up because the current pricing ends on September 15, 2026.

Pointics lets WordPress businesses reward customer actions such as purchases, reviews, referrals, repeat orders, and other engagement with points and rewards.

It’s designed to go beyond the usual WooCommerce-only loyalty setup, with use cases for digital product sellers, event businesses, booking businesses, restaurants, LMS sites, and more.

Current Early Bird pricing until September 15:

• Standard: $59
• Premium: $119
• Agency: $199

From September 16 to September 30:

• Standard: $69
• Premium: $129
• Agency: $229

So if you were already considering Pointics, September 15 is the last day to get the current Early Bird pricing.

You can check it out here:
https://themewinter.com/pointics/

Since this is still a relatively new product, feedback from WordPress users is genuinely useful for us too.

If you run a WordPress business, what kind of customer action would you actually want a loyalty plugin to reward besides purchases?

I've been doing website admin work for about 30 years, and I drive long-haul freight for a living now. Plugin development happens in truck stops during my off-duty hours.

I want to talk about the part that was actually interesting to build, which is that WordPress 7.0 handles AI provider connections itself now under Settings → Connectors. My plugin never asks for an API key, never stores one, never transmits one. It just uses whatever you've already connected. You can wire up Google, OpenAI, and Anthropic side by side, and the plugin requests writing capability and image capability separately, so pairing a strong long-form model with a different image model works without any configuration on my end.

Honestly this changed how I thought about the whole category. Most AI content plugins are a thin client wrapped around the vendor's own backend and their own margin on inference. Building against core Connectors means there's no backend at all. Nothing leaves your host. If you uninstall it, your posts and drafts stay put.

The other piece I spent the most time on: every citation gets fetched and confirmed to return a live response before it's rendered as a link. If the model invented a URL that doesn't resolve, it gets discarded. That's checked in code, not requested in a prompt, which is the only way I could find to make hallucinated sources structurally impossible rather than merely discouraged.

Defaults are draft-only behind a human review gate, near-duplicate detection blocks a draft too close to something you've already published, and there are one-click bulk noindex and bulk unpublish tools because sometimes you need to walk a content program back.

Two honest caveats:

It requires WordPress 7.0 and PHP 8.1. Almost nobody is on 7.0 yet, so realistically this is early. I built for where WordPress is going rather than where it is.

There's a paid tier, but the free version on the .org repo does full generation. I'm not going to pretend otherwise.

https://wordpress.org/plugins/waypoint-seo-content-generator/

Mostly posting because I'd like feedback from people who've built against Connectors. The capability negotiation API in particular felt underdocumented and I'm not sure I'm using it the way it was intended. Happy to answer anything about the plugin review process too, that took a while.

A while ago I shared ACE Product Filters here when I released v1.0 (See the post here)

The original idea was pretty simple: I wanted a WooCommerce filtering plugin that covered the features I actually needed, without having to compromise on functionality, styling, or how the filters worked together.

Since then, I've kept developing it through several releases, and it's grown quite a bit.

So rather than making another "I built a plugin" post, I thought I'd share what has changed.

🔎 New: Instant Product Search

The biggest addition in 1.3 is a completely separate instant product search.

You can now add a search box to a header, homepage, landing page, or anywhere else on your site.

As the visitor types, products appear instantly in a dropdown with:

• Product image
• Product name
• Price
• Optional SKU

You can choose whether to search by product title, SKU, or both, and optionally limit the search to specific categories, tags, attributes, or other product taxonomies.

It also has its own Elementor widget and shortcode, separate from the filtering system.

So you can use product filtering when someone wants to narrow down a catalog, and product search when they already know what they're looking for.

🧩 A lot more filtering functionality since v1.0

The filtering system itself has also grown considerably.

You can now filter WooCommerce products by:

• Categories, attributes and product taxonomies
• Price
• On sale
• Stock status
• Rating
• Featured products

There is also:

• Single-select or multi-select filters
• AND / OR matching
• Parent/child term selection
• Product counts, including contextual counts
• Hide terms with no matching products
• Search within long filter lists
• Colour swatches
• Custom filter panels and grouped headings
• Collapsible filters
• Responsive/mobile layouts
• AJAX filtering with URL state and browser history
• Elementor widgets and shortcodes

The dashboard and filter editor have also gone through several UX improvements, including a live appearance preview and more control over how filters and panels behave.

🎨 Built to actually fit the website

One thing I've always wanted to avoid with filter plugins is having a functional filter that then looks completely out of place on the website.

So there are quite a few controls for the appearance of filters, panels, swatches, search boxes and search results, including responsive/mobile presentation.

You can use individual filters, or combine multiple saved filters into reusable panels for things like shop sidebars, top bars, or custom Elementor layouts.

💸 And yes — it's still completely free

All the filtering features are and always will be completely free.

I do plan to eventually introduce an optional Pro version sometime in the future, but if and when I will introduce it, will be focused on additional workflow and business-oriented tools for people who need them — while the actual filtering experience (present and future) remains available to everyone.

🚀 And there's now a second plugin

While working on ACE Product Filters, I realized that the same problem exists outside WooCommerce.

So I recently released ACE Content Filters, a separate free plugin for filtering posts, pages and custom post types.

It brings the same concept to things like blogs, portfolios, directories, events, jobs, real estate, courses, knowledge bases, etc., with taxonomy, search, author and date filters — plus instant content search.

I'll probably make a separate post about that one rather than turning this into an even longer feature list.

If you've seen the original post or have tried ACE Product Filters since then, I'd genuinely appreciate any feedback.

I'm still actively developing it, so I'm particularly interested in what features or improvements would actually be useful for real WooCommerce stores.

ACE Product Filters:
https://wordpress.org/plugins/ace-products-filters/

ACE Content Filters:
https://wordpress.org/plugins/ace-content-filters/