Automations email content editor loads completely blank
-
(no errors, ruled out all other plugins)
Hi there,
I’m running into an issue where the MailPoet email content editor won’t render at all. Details below — I’ve done a fair amount of troubleshooting already, so hopefully this saves some back-and-forth.
Environment:
- WordPress 7.1
- Divi theme
- MailPoet 5.37.0
- Hosted on Hostinger
The issue:
When editing an email’s content (via Automations → [an automation] → Send email step → Edit content, which opens the standardpost.php?post={id}&action=editscreen for themailpoet_emailpost type), the page loads normally — admin sidebar, top toolbar, “Screen Options” button all render — but the actual block editor canvas underneath stays completely blank. No editor UI ever appears, regardless of how long I wait.What I’ve already checked:
- No JavaScript console errors at any point during page load
- No MailPoet-related network requests fire at all when the page loads — I checked the browser’s network tab and there isn’t even an attempt to load MailPoet’s editor JS bundle, which suggests something is preventing it from being enqueued rather than it failing after loading
- Ruled out every other active plugin as a conflict. I systematically deactivated all 16 other active plugins on the site — individually, and as a full batch for the WooCommerce + extensions cluster — and retested after each one, restoring it before moving to the next. The blank editor persisted through every single test, including with MailPoet as the only active plugin besides required core functionality. Full list tested: Jetpack, LiteSpeed Cache, Yoast SEO, Forminator, Site Kit by Google, Safe SVG, Copy & Delete Posts, WP Date and Time Shortcode, Printful integration, and WooCommerce plus WooCommerce Payments/Shipping/Tax/PayPal Payments/Stripe Tax.
- Haven’t yet tested switching away from the Divi theme — that’s a bigger change I wanted to check with you before making, since it affects the live site. Is this a known Divi-specific conflict?
- The underlying email content itself is fine — I confirmed this by editing the post content directly through the WP REST API (
/wp/v2/mailpoet_email/{id}) as a workaround, and by using MailPoet’s own “Preview” function in the automation step, which renders the email correctly. So this seems isolated specifically to the block editor UI failing to load, not a data/content issue.
What I’m hoping to find out:
- Is this a known issue with Divi specifically, or any other theme?
- Is there a server-side requirement (PHP memory limit, execution timeout, etc.) that could cause the editor bundle to silently fail to enqueue without throwing a JS error?
- Any other diagnostic steps you’d recommend before I try a theme switch test?
Happy to provide screenshots, a screen recording, or admin access if that helps speed things up.
Thanks,
Michael
You must be logged in to reply to this topic.