Yes. The plugin extends the core WordPress Navigation block using standard block editor APIs. It works with any block-based theme (like Twenty Twenty-Four, Kadence, Blocksy, GeneratePress block version, etc.).

Hybrid themes that include a Navigation block in their templates also work. Classic themes that use wp_nav_menu() for navigation will not be compatible — those don’t use the block editor navigation system.

Unlikely. All styles are scoped to a unique ID per navigation block instance (e.g. #cw-nav-1), so they only affect the block they’re attached to and won’t bleed into other elements.

The plugin uses !important selectively to override WordPress’s own cascade where necessary. In rare cases where a theme uses inline styles on nav elements, those may rank higher — see the troubleshooting guide for how to diagnose this.

No — and it won’t work with page builder nav menus either. This plugin is specifically designed for the native WordPress block editor Navigation block.

If you’re using Elementor’s nav widget or Divi’s menu module, those are separate elements and this plugin won’t add controls to them.

WordPress 6.0 or higher is required. This is when the Navigation block reached a stable, consistent state with the inspector controls API the plugin relies on.

We recommend running the latest stable WordPress release. The plugin is tested against new WordPress versions as they release.

No. The classic editor predates the block system entirely and doesn’t use the Navigation block. This plugin requires the block editor (Gutenberg) to be active.

Free includes hover text color, hover background color, selected text color, and selected background color for top-level navigation items. These cover the majority of everyday use cases.

Pro adds: submenu and overlay colors, parent with submenu hover colors, item padding, gap and spacing controls, submenu separator, item borders (6 states with full BorderBoxControl and BorderRadiusControl), all typography controls including font family (5 panels), full mobile menu styling with spacing and font controls, close button styling, and responsive visibility per item (hide on desktop, tablet, or mobile independently).

Yes. Color changes preview in real-time in the Site Editor. The editor uses CSS custom properties set on a wrapper element, so you’ll see the result as soon as you pick a color — no save required to preview.

Note that hover states (which require mouse interaction) are harder to preview inside the editor since the editor intercepts click events. The best way to verify hover colors is to save and check the frontend.

Yes. Each Navigation block instance stores its own settings independently as block attributes. You could have a header nav with blue hover colors and a footer nav with no custom colors at all — they’re completely separate.

Color, typography, border, and spacing controls apply to all items in the navigation block uniformly. Per-item color overrides are on the roadmap but not yet available.

However, Responsive Visibility is per-item — you can independently hide any individual link or submenu on desktop, tablet, or mobile. This lets you show different items at different breakpoints without maintaining separate menus.

Each nav item (link or submenu) has three independent toggles: Hide on Desktop, Hide on Tablet, and Hide on Mobile. Select the individual item in the block editor — not the parent Navigation block — to see these toggles in the Settings panel.

You can activate any combination. If an item is hidden on mobile and tablet, it only appears on desktop. The visibility is applied via CSS classes and has no JavaScript overhead.

When all children of a submenu item are hidden on a given breakpoint, the plugin automatically hides the parent’s dropdown arrow on that breakpoint too — so no ghost indicator is left behind.

Yes. Pro includes full border control for six states: top-level normal, hover, and active, plus submenu normal, hover, and active. Each state has an independent BorderBoxControl (color, style, and width — linked or per-side) and a BorderRadiusControl (linked or per corner).

Top-level borders are automatically scoped out of the mobile overlay so desktop box styles don’t bleed into the stacked vertical mobile menu.

Yes, intentionally. The plugin wraps the link and arrow button in a shared container element (.cw-nav-item-wrapper) so the background color covers both. This avoids the common visual glitch where the hover background only covers the text link, leaving the arrow floating on a different background.

Pro is an annual license. When you purchase, you receive a license key that activates Pro features on one WordPress site. Your license includes automatic plugin updates and priority email support for 12 months.

At renewal, you can continue at the then-current rate or let it lapse — if you don’t renew, the plugin continues working but won’t receive updates and you lose access to priority support.

Yes. The free version is GPL licensed and can be used on any number of sites without restriction. You can also redistribute it freely under the GPL terms.

Each Pro license covers one domain. If you’re building for clients, you’d need a license per client site. If you manage many client sites, contact us about agency pricing.

Yes. We offer a 14-day refund on Pro licenses, no questions asked. If the plugin doesn’t work as expected for your use case, contact support within 14 days of purchase for a full refund.

Please view our refund policy for more information.

Nothing breaks. The plugin continues to work exactly as it did — all your settings are preserved and all Pro features remain active. You just won’t receive automatic updates or priority support access until you renew.

We recommend keeping the license active to stay current with WordPress compatibility updates.

First, make sure you’ve selected the Navigation block itself — not a child block inside it like a Navigation Item or Page List. Click directly on the nav container; the block label in the top-left of the editor should say “Navigation”.

Then open the right sidebar (⚙ icon, top-right) and click the Styles tab (paint roller icon). The plugin controls appear in panels labeled “Hover/Selected” and “Mobile” at the bottom of the Styles panel.

Make sure you’ve clicked Save in the Site Editor. Block attributes are only written to the database on save — unsaved changes won’t appear on the frontend.

If you’ve saved and it’s still not showing, try clearing your browser cache and any caching plugins (WP Rocket, W3 Total Cache, etc.). The plugin injects styles at render time, so a cached page may not have the new styles.

Open browser DevTools (F12), right-click the affected element and choose Inspect, then look at the Styles panel on the right. Find the property being overridden and check which rule is “winning” — it will show the file/line it comes from.

If the winning rule uses !important with a more specific selector, you may need a small CSS snippet in your theme’s Additional CSS to counter it. Contact support and we can help diagnose the specific conflict.

This is most commonly a PHP version issue. The plugin requires PHP 7.4 or higher. Check your PHP version in WordPress admin under Tools → Site Health → Info → Server.

If you’re on a compatible PHP version and still seeing errors, please contact support with the full error message and your WordPress/PHP versions.