LABS brings together five WP Quick Tools modules for interactions, languages, business hours, and navigation. Choose those useful to your project and configure them individually, staying in control of which features are active.
These tools should be evaluated in the context of your site. Start in a test environment, keep a backup, and check the result with your theme, builder, and plugins. Unlocking and activation are separate steps: making a module available does not mean it has already been enabled.
Connect a trigger element to one or more target elements through CSS classes. When the pointer enters the trigger, the target appears with a fade and movement; when it leaves, the target becomes hidden again. You can create multiple interactions, adjust duration, easing, and horizontal or vertical offset, and choose the active class.
The module also handles focus and blur, but the trigger must be keyboard-accessible. Always test the interaction on touch devices and do not rely on a mouseover-only effect for essential information.
Adds a compact selector with language codes such as IT, EN, and DE. It displays alternatives with an available translation for the current page, excluding the active language. Use the shortcode [wqt_wpml_lang_selector] in an area that executes WordPress shortcodes.
It requires WPML and translations already set up. If no alternative languages are available, the selector produces no links.
Displays Open/Closed status and information about the next opening or closing based on the configured hours. You can define up to two daily time slots, closure dates, and days with special hours. The time zone can be the site’s or a specific one, such as Europe/Rome.
The shortcode [wqt_business_hours] displays the status message. Options allow you to add a title or show the hours table. Time slots spanning midnight are not supported.
Selects the frontend menu based on the page context. You can use content or term metadata, the root page, post type archives, URL paths, and contexts such as search or a 404 page. Configurable weights determine which rule takes precedence.
It is suitable, for example, for a site with sections or divisions requiring different navigation. It requires mapping contexts to menus or theme locations, with fallbacks to check before use.
Makes selected public custom post types and taxonomies available in Appearance > Menus. You can then add individual content items and terms available on the site to the menu, using the classic menu interface.
The module does not create new post types or taxonomies: it works with those registered by the theme or plugins that are public and have an admin interface.
Identify the result you want: an interaction, a language switch, opening status, or different navigation. Start with one module so you can easily distinguish its effect from the site’s other features.
Keep a backup and use a test page or environment. For modules that affect menus, note the current assignments and prepare fallback navigation.
Open the LABS group in WP Quick Tools. If necessary, unlock the module and then enable it with its switch. Unlocking does not replace activation.
Configure only the relevant options and save. For Mouseover Dissolve, assign classes to the relevant elements. For the WPML selector and business hours, insert the shortcode. For menus, check post types, theme locations, rules, and assignments.
Check desktop, mobile, and keyboard use. On a multilingual site, test translated pages. For business hours, check time zones, breaks, and closures; for menus, also test pages without a specific rule, search, and archives.
If a module does not produce the desired result, disable it and review the configuration. Before using it on the public site, verify that content and navigation remain usable even in less common scenarios.
Five modules: Mouseover Dissolve, WPML Language Selector, Business Hours (Live), Contextual Menu Resolver, and Content in Menus. Each addresses a different need and can be configured and enabled separately.
No. Enable only those your project needs. Unlocking makes a module available, while its switch controls activation. Settings must be saved after configuration.
Assign the classes configured in the rule to the trigger and target. The module makes the target visible when it receives the interaction from the trigger. Use specific classes to avoid affecting other elements. The data-wqt-mouseover-target attribute on the trigger can specify an alternative target selector.
The code listens for focus and blur as well as mouse entry and exit. Keyboard use requires a genuinely focusable trigger, such as a link or button. There is no dedicated touch command: check behavior on the relevant devices and do not hide essential information behind hover alone.
The selector excludes the current language and languages without an available translation of the page. If WPML is unavailable or there are no valid alternatives, it shows no links. Check the page’s translations and associations before changing the layout.
The shortcode supports the separator and class attributes. For example, [wqt_wpml_lang_selector separator=” / “] separates language codes with a slash. The class attribute lets you assign a class for styling. The module does not create translations.
Insert [wqt_business_hours] in an area that executes shortcodes. You can use [wqt_business_hours mode=”table”] for the table or [wqt_business_hours show_schedule=”1″] to include the schedule. Configure time slots, time zone, closures, and badge text first.
You can set up to two time slots per day and specific dates for closures or special hours. A date listed as a closure takes precedence over special hours for that same day; without exceptions, the normal weekly schedule applies. Time slots spanning midnight are not supported.
The module provides synchronization with the server and the configured time zone. Live operation requires JavaScript and access to the endpoints used by the module. Check that caching, firewalls, or optimizations do not prevent status updates.
It evaluates enabled rules and compares their weights. The resulting context is mapped to a menu or theme location; the configuration also includes fallbacks. The module affects menus that go through wp_nav_menu and the configured target locations, not every navigation system built by a builder.
No. It makes the panels for selected public custom post types and taxonomies available. In Appearance > Menus, you then choose the individual items to add and save the menu. Posts, pages, and native taxonomies remain managed by WordPress.
The result depends on the site and the integrations actually used. Some modules require CSS classes, shortcodes, WPML, or the classic menu system. Test them in the relevant environment before publishing: this collection does not imply universal compatibility certification.
Disable the relevant module in the WP Quick Tools panel and check the affected pages. Remove or adapt any shortcodes and check menu assignments you changed during the test. Disabling is not equivalent to restoring a full site backup.