← Integrations

Static Shield + JupiterX

JupiterX (by Artbees) is a full rewrite of the older "Jupiter" theme, and has no page-building engine of its own — it's built as an Elementor extension, requiring the real, separate Elementor plugin. What's specific to JupiterX on top of Elementor's own compatibility: a mega menu that renders statically, three confirmed pagination/lazy-load AJAX bridges, and a site-wide maintenance-mode toggle worth knowing about.

Recommended mode

Static + Bridges

Static behavior

Core page rendering is Elementor's (see the Elementor integration for that part). JupiterX's own mega menu renders synchronously server-side — no AJAX call — so it's static-friendly as long as Advanced Custom Fields, which the mega menu depends on for its template assignment, stays active.

Dynamic behavior

A site-wide maintenance-mode toggle checks both Elementor's and JupiterX's own settings on every front-end request and can swap the entire page template for visitors — a publish-time decision to plan around, not a per-route policy. A weekly license-check cron job also exists, but it's favorable for static serving: it only fires on real HTTP hits to the origin, which happen far less often once a static release is doing the serving.

Bridges & routes

Three confirmed public AJAX actions, each pagination/lazy-load only (never the first paint): WooCommerce grid "Load More" (only present when WooCommerce is active), popup content fetched at trigger time, and Raven Loop Grid widget pagination.

Setup

No special setup — detected automatically across the theme, its child theme, and the JupiterX Core plugin. Requires the separate Elementor plugin to be active, same as JupiterX itself does.

Limitations

This classification is rule-derived from reading JupiterX 4.60.0's actual source (theme, child theme, and JupiterX Core plugin) against a live install, not from running an automated end-to-end test. Several other bundled Raven widgets (advanced posts, products, product gallery, tabs) register similar public AJAX handlers that weren't individually confirmed to be pagination-only the way Loop Grid was — treat those as needing their own check before assuming identical behavior.