8.5 Compatibility
Lifter Elements' requirements, the integrations it is built for, and any known conflicts.
Requirements
Lifter Elements requires the following to be installed and active:
| Software | Requirement |
|---|---|
| LifterLMS | Required (active) |
| Elementor | Required (active). 3.5.0 or later; a current release recommended |
| Elementor Pro | Recommended. Required for some widgets (see below). When it is active it must be 3.5.0 or later; an older Pro shows a warning in the admin |
| LifterLMS Groups | Required for group features, with Lifter Elements 1.7.0 or later |
| WordPress | 6.8 or later |
| PHP | 7.4 or later (enforced minimum); developed and tested against PHP 8.2 |
These are the floors Lifter Elements checks on activation as of 1.7.7. With an older WordPress, PHP or Elementor the plugin shows an admin notice and does not load.
A few widgets depend on Elementor Pro and won't render fully without it:
- Course Access Plans — uses Elementor Pro's Carousel widget
- Course Author — uses Elementor Pro's Carousel widget
Supported integrations
Lifter Elements is built for and tested with LifterLMS and Elementor. It also integrates with:
- Elementor Pro — enables the Pro-dependent widgets above and the wider Elementor feature set
- LifterLMS Groups — brings group functionality (widgets, dynamic tags, conditional-logic conditions, and seat-based purchasing) into the Elementor design surface. As of Lifter Elements 1.7.0 this integration is built into core; no separate add-on plugin from Tangible is required, only the LifterLMS Groups add-on from LifterLMS itself.
These are its documented integrations.
Known conflicts & special handling
This section is being compiled from real support cases. Known conflicts and any special handling (for example multilingual plugins, caching plugins, or specific themes) will be documented here as they are confirmed.
Support scope
Support covers one active domain per license and focuses on issues within Lifter Elements itself. Compatibility with third-party plugins or themes outside the documented integrations above is not guaranteed. See the FAQ for licensing and support details.