Repository navigation
FAQ English
For single WordPress sites and Multisite networks. Both have been supported since 2012.
No. Single WordPress sites and Multisite networks have both been supported since the first release in 2012. On a single site, you can use the configurable toolbar menu, plugin/theme ZIP uploaders, menu preview and settings. Multisite adds network administration and shared-menu features.
Single site: Settings → Toolbar Additions. Network activation: Network Admin → Settings → Toolbar Additions. With site-only activation in Multisite, a super administrator uses the active website’s Settings → Toolbar Additions; settings still apply to the network.
Create a normal navigation menu and select its source site and menu in the settings. Network activation defaults to the main website; site-only activation defaults to the active website. Activate the plugin on the source website or across the network so that shared-menu protection can run. The legacy mstba_menu location remains a fallback.
The name of the selected WordPress menu. Leave the custom label empty to keep this automatic title.
Yes: first, last, before or after a selected toolbar item, or on the right. Choose frontend, admin or both, and the permitted audience. If an anchor is missing, the menu falls back to the end.
One child level includes direct children; two includes their children too. Zero means all available levels. The configurable limit is ten child levels.
WordPress must display its toolbar for the current user. Also check the plugin switch, audience, frontend visibility, source site and selected menu. The plugin does not force the toolbar on for visitors.
Yes. The plugin respects WordPress’s user-profile preference for displaying the toolbar on the frontend. It does not enable the frontend toolbar for someone who has hidden it. Menu source, position and shortcut configuration remain site/network settings.
No. It shows saved settings without JavaScript. With JavaScript, changing a menu control updates a signed read-only preview of unsaved values. Only Save changes persists settings. Preview entries do not navigate to destinations. The preview shows up to 200 entries without limiting the actual toolbar menu. The anchor check describes the current page, not all frontend or administration contexts. Use Save all changes in the sticky bar to apply settings. Changed form values are marked, and leaving or reloading warns before discarding them. Reverting edits clears the warning. The simplified dark toolbar model has keyboard-accessible expandable groups; the effective-settings summary follows it.
The toolbar audience and permission to edit its source menu are separate. Shared Multisite source menus are protected against unauthorized admin, REST and Customizer changes.
Both Plugin ZIP and Theme ZIP admin submenu links are enabled. The previous hidden Theme submenu default transitions once; the next save records the transition and later explicit disabled choices remain effective. Under New, Plugins remain enabled and Themes disabled. Each addition has its own switch. Themes follows Plugins directly in the website toolbar menu, including Multisite.
Plugin and theme additions are moved to the end of the + New group, including after late-registered content types. WordPress capabilities still determine availability.
When Leitstand is active and its uploader is accessible to you, the toolbar and admin menu use its pages without duplicate upload screens. Otherwise this plugin provides its own pages with drag-and-drop, size validation and temporary metadata previews. WordPress handles installation and replacement. Native uploads work directly without JavaScript. Previews are not malware scans or compatibility guarantees and do not use the Leitstand usage index. Multisite files are shared across all websites and networks; installation remains restricted to authorized users. Leitstand user exclusions are respected. This plugin’s switches control its own menu links, not existing Leitstand entries. Choose one ZIP, review its metadata, confirm the package and use Install plugin now or Install theme now beneath the result. No installation happens during preview. The uploader switch is separate navigation. More space separates the footer from the workflow. An unambiguously detected theme in the plugin uploader, or plugin in the theme uploader, shows a discreet notice and a link to the correct uploader. Known mismatches provide no installation action on that page; ambiguous packages are not assigned a misleading type.
A shared installer tab for approved deckerweb plugins. Library 0.6.0 checks package hashes and dependencies, separates installation from activation and uses one elected runtime across participating hosts. The offline catalog includes a preparation preview; online catalog updates are optional and off by default. In Multisite, network-activate a participating host to make the Library available in Network Admin.
No. Its bundled catalog and artwork work locally. Package downloads contact their declared hosts when requested. Optional online catalog retrieval is disabled by default and uses caching and backoff when enabled.
The bundled deckerweb Updater 2.1.0 checks this fixed public repository and caches release metadata. WordPress controls individual, bulk and automatic updates. The plugin does not enable automatic updates. Packages must match the offered version, plugin identity and platform requirements before replacing the installed copy.
Deactivation keeps all settings and WordPress menus. Uninstall clears this plugin’s update cache. Toolbar settings are retained unless the deletion option is enabled for that site or network. On physical removal every network’s own choice is respected. Shared Library cleanup runs only after its last installed host is removed, including inactive hosts; its own deletion option is separate. Installed plugins, navigation menus and foreign content remain untouched.
WordPress 6.7 or newer and PHP 8.2 or newer. Local integration checks use PHP 8.4; CI also checks PHP 8.2. No PHP 7 compatibility is declared.
Yes: existing navigation menus remain in WordPress. The legacy mstba_menu location is still recognized. Review the new settings and optional shortcuts after the first upgrade. Keep a backup before replacing a major version.
Shortcuts depend on permissions, installed integrations, Multisite context and theme capabilities. Block themes offer the Site Editor; classic themes offer their applicable customization screens. File editor links are opt-in and respect WordPress restrictions.
Menu data is reused within the request, sites are bounded by the configurable subsite limit, and frontend assets load only when needed. There is no full-network scan on every page. Exact speed still depends on your WordPress installation and other plugins.
For ordinary questions and bugs, use GitHub Issues or Discussions. For suspected vulnerabilities, use the repository’s private security report form; see SECURITY.md. Include plugin, Library, WordPress and PHP versions plus redacted reproduction steps. Never include credentials or private content.
Multisite Toolbar Additions
English
Deutsch