ElementsKit plugin review and common issues

ElementsKit Mega Menu uses grid layouts for its multi-column dropdown. On mobile: (1) in the ElementsKit Mega Menu Builder, check if mobile-specific settings are available for your menu item — some menu items can be configured to show as a standard dropdown on mobile; (2) use CSS media queries to override the mega menu grid on small screens (set columns to 1 on mobile); (3) consider keeping the mega menu for desktop and a simplified menu for mobile by using Elementor’s responsive visibility to show different navigation elements on different device sizes.

After designing the header in ElementsKit → Header Footer Builder, the header must be assigned as the active header for the site. In ElementsKit → Header Footer Builder, click the three dots on your header design and select “Conditions.” Set conditions for where this header should display (all pages, specific pages, specific post types). Ensure the condition covers the pages you want and save. If the theme header still shows, your theme may be outputting the header before WordPress’s get_header() hook — check ElementsKit’s compatibility notes for your specific theme.

Blank widget rendering usually indicates a JavaScript or CSS asset loading failure. Check: (1) ElementsKit → Elements and verify the specific widget is enabled; (2) Elementor → Tools → Regenerate CSS and Flush Cache; (3) browser DevTools Console for JavaScript errors; (4) disable browser caching (hard refresh with Ctrl+Shift+R) to ensure fresh assets load; (5) verify ElementsKit version compatibility with your Elementor version. Some widget rendering issues were resolved in ElementsKit updates — ensure you are on the latest version.

In Appearance → Menus, create or edit a menu item. In the menu item settings, enable ElementsKit Mega Menu for that item. Select the mega menu layout (number of columns) and click “Edit Mega Menu” to open the Elementor-based mega menu builder. In the Mega Menu builder, add columns and fill each with ElementsKit widgets — use Image widgets for featured images, Heading and Text for descriptions, Navigation widgets for sub-menu links, and Button widgets for CTAs. Save the mega menu. When visitors hover the parent menu item, the full-width mega dropdown displays your Elementor-built content.

Go to ElementsKit → Starter Sites. Browse the available starter sites by category (business, agency, portfolio, restaurant, etc.). Click “Preview” to see a full-site preview. Click “Import” to begin the one-click import — this imports all pages, the homepage template, the menu, widgets, and customizer settings for the starter site. The import process may take several minutes and requires a stable internet connection. After import, replace placeholder content (text, images, logo) with your actual content. Starter sites are designed for the Elementor + ElementsKit combination.

ElementsKit’s bundled Header Footer Builder and Mega Menu Builder make it the more self-contained choice for sites that need custom navigation infrastructure alongside Elementor widgets. Essential Addons provides more widgets but does not include header/footer building or mega menu functionality — you would need additional plugins (like Elementor Pro’s Theme Builder for headers, or Max Mega Menu) to match ElementsKit’s infrastructure. If navigation customization is a core requirement, ElementsKit’s all-in-one approach is the more efficient solution.

ElementsKit works with both Elementor free and Elementor Pro. The Header Footer Builder in ElementsKit is particularly useful for Elementor free users who lack access to Elementor Pro’s Theme Builder — it provides similar header/footer customization capability without the Pro upgrade. However, some advanced features in ElementsKit (like the full Template Library access) work best when paired with Elementor Pro. For most widget and mega menu use cases, ElementsKit functions fully with Elementor free.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.