Using AjaxPress With Elementor, Bricks and Divi: Setup, Templates and Known Issues
EDITOR NOTE — remove before publishing. Bricks edit-screen and Divi 5 issues are open as of 2.4.2. This post deliberately contradicts the current readme’s compatibility claims — reconcile both together.
Page builders and single page applications both want control of the same things: the DOM, script execution, and what happens when you click. Mostly they coexist fine. In a few specific places they don’t, and it’s better to tell you where than to let you find out.
The rule that applies to every builder
Anything you want to survive navigation must live in a global template, not on a page.
Every builder distinguishes between page content and site-wide templates. Page content is exactly what gets replaced when someone navigates, so a radio player or sticky bar dropped onto a page will vanish the moment a visitor clicks a link. Put it in the footer template instead. That single decision resolves most “it stops working when I navigate” reports.
Elementor
The most common builder in our support inbox, usually with Hello Elementor, and the pairing generally works well.
Persistent player setup
- Go to Templates → Theme Builder → Footer and edit your site footer.
- Add your audio widget, or an HTML widget containing your player.
- Select it, open Advanced → CSS ID, set something like
my-radio-player. - In Settings → AjaxPress → Advanced → Media Players, enter
#my-radio-player. - Give it self-contained positioning — Elementor widgets are usually styled through their parent section, and once the player is moved out, those styles stop applying.
Known issue: Elementor Pro Forms
An open bug, reported in detail by a Pro customer, worth knowing before you rely on forms.
On a page with an Elementor Pro Form, submitting can complete only partway. The entry saves — Collect Submissions works — but “Actions After Submit” such as the Email action may never run, and submit_success never fires. It’s a race condition, so it’s intermittent and more likely under server load.
The cause is that AjaxPress listens for form submissions to handle them over ajax, and on Elementor Pro forms that can run in parallel with Elementor’s own handler.
Workaround: add the form’s page to Advanced → Exclude Links. Note the trade-off — excluded pages don’t fire ajaxpress:ready, so a player or script that initialises on that event won’t run there either. If your form page also has a player, you currently have to choose. We know. It’s being fixed.
Standard Elementor forms, Contact Form 7, WPForms and Fluent Forms have not shown this behaviour.
Bricks Builder
The front end works. The edit screen has an open issue.
With SPA for Admin Dashboard enabled, Bricks edit screens have been reported as failing to render — you open a page to edit and get a blank or broken builder.
Fix, and a good default anyway: go to Settings → AjaxPress → Basic and turn SPA for Admin Dashboard off. Visitors see no difference — that setting only affects wp-admin. Builder edit screens then load normally.
On WordPress 7.0 and newer we recommend leaving it off regardless, since WordPress now handles dashboard navigation itself.
For a persistent player, build a global footer template in Bricks, give your player element a CSS ID, and use that as your selector.
Divi and Divi 5
Same shape of problem. Divi 5 Builder has been reported as not working correctly with AjaxPress, again around the builder rather than the front end.
Turn SPA for Admin Dashboard off first — that resolves most of it. If you still see problems editing with Divi 5 specifically, email us with your Divi version. Divi 5 is a significant rewrite and we don’t yet have the coverage we’d like.
For the front end, use the Divi Theme Builder to add a global footer, and give your player module a CSS ID under Advanced → CSS ID & Classes.
A note on our compatibility claims
Our plugin listing says AjaxPress is tested with Bricks, Divi Builder and Elementor Forms. As you’ve just read, all three have open issues. That’s a gap between what we’ve claimed and what some users experience, and we’re closing it — both by fixing the bugs and by being more careful about what “tested” means.
We’d rather you read that here than discover it on your own site.
Quick troubleshooting
| Symptom | Try first |
|---|---|
| Builder edit screen won’t load | Turn off SPA for Admin Dashboard |
| Player disappears on navigation | Move it into a global footer template |
| Player moves to the wrong place | Give it its own position: fixed CSS |
| Widget animations only run once | Re-initialise on ajaxpress:ready |
| Elementor Pro form emails not sending | Known issue — exclude that page for now |
| Styles missing after navigation | Check whether they were scoped to a parent the element no longer has |
Tell us what breaks
Email [email protected] with your builder and version, your theme, whether SPA for Admin Dashboard is on, and a URL where we can see it. Builder issues are very version-specific, so the version number genuinely matters.