Repository navigation
FAQ
ACF Free/Pro, Meta Box with available extensions, JetEngine, ACPT Free/Pro and Pods. Toolset and Secure Custom Fields are also supported. Several compatible providers can appear together.
It opens existing administration pages. Field definitions, content, roles and provider configuration remain under the provider’s control.
The required provider or module may be inactive, its admin menu unavailable, or the current user may lack permission. Check the provider, destination and add-on switches, as well as role and user exclusions for this website.
Open Settings → Types & Fields QuickNav → Add-ons → Extensions for ACF. Enable the desired add-on. ACF Extended requires ACF Pro. An active add-on and its QuickNav visibility are independent states.
Yes. Under General, select excluded roles or enter exact WordPress usernames. Any matching role or user exclusion hides the complete QuickNav toolbar entry in the administration area and frontend. Authorized administrators retain access through the WordPress Settings menu.
Frontend navigation is off by default. When enabled, it includes verified definition post types and optional content lists; menu-based provider screens remain administration-only. Each multisite website keeps its own settings and exclusions.
Settings are retained by default. Each website may opt in to deleting its own QuickNav settings on uninstall. Provider content and data are never removed. Shared Library cleanup follows its own settings and last-host rules.
Yes. General offers 20 local Lucide symbols. The default remains Layers. Provider icons are distinct and text labels remain accessible. You can also rename the main toolbar entry; leave the label empty to restore its translated default.
Enable content navigation, then check the lists you want to show. Existing exclusions are converted without changing the current selection. New types stay unselected after saving. Switching the feature off retains your choices.
Yes, compatible active providers receive independent branches. Do not load ACF and its API-sharing fork together.
No. Each available feature is checked independently, including individual modules and All-in-One.
Activation and navigation availability are separate. The required provider, administration screen and permission must all be available.
No. It opens the vendor administration screen. Only that provider controls subsequent actions.
Their reviewed modules may use tabs in Toolset settings. QuickNav links to the available tab when its runtime and native permission checks succeed.
Their entire QuickNav entry disappears. The WordPress Settings menu still provides access to authorized accounts with manage_options.
No. QuickNav never grants provider permissions. Role and user exclusions can only further restrict its own toolbar visibility.
No. Each website keeps its own settings, including role and user exclusions.
No. The bundled updater uses published GitHub releases in the WordPress update workflow. Draft releases are excluded; automatic updates are not enabled by installing QuickNav.
No. Obtain supported providers and licenses from their vendors.
See Data and privacy and Settings.
Switch between Providers and navigation, Add-ons and General. Each tab has its own URL and works without JavaScript; saving changes only that section.
CPT UI manages post types and taxonomies. Field groups belong to a field provider such as ACF or Meta Box. Both families can be active together.
Yes. Each save changes only the selected section. Save your edits before switching to another tab.
Types & Fields QuickNav · Documentation / Dokumentation
Website / Website · Wiki home / Wiki-Startseite · Repository · Downloads & Releases
Help & bugs / Hilfe & Fehler · Discussions / Austausch · Security / Sicherheit
© 2026 David Decker – DECKERWEB.
Plugin: GPL v2 or later / GPL v2 oder höher.