Blank block editor / Customizer
-
Hi PayPal Payments team,
We’ve found a reproducible conflict between WooCommerce PayPal Payments and the Latitude Interest Free Gateway for WooCommerce plugin (also listed as “Latitude Payment App Gateway for WooCommerce”). When both are active, every admin screen that uses the block editor loads as a blank white page.
ENVIRONMENT
- WordPress: [version]
- WooCommerce: 11.2.1
- WooCommerce PayPal Payments: reproduced on 4.1.3, 4.2.0 and 4.2.2
- Latitude Interest Free Gateway for WooCommerce: 2.0.2 (latest)
- PHP 8.2, 256M memory limit, Kinsta hosting
- Theme: Porto (child); also reproduced with Twenty Twenty-Five in Health Check troubleshooting mode
AFFECTED SCREENS (all return a blank page)
- Pages / Posts > Add New, and editing existing pages and posts
- Any custom post type that uses the block editor (e.g. Porto Builder, FAQs)
- Appearance > Customize
- Appearance > Widgets
- Site Editor
- Reusable blocks / patterns
Not affected: product, order and coupon screens, WooCommerce settings, the Elementor editor, and the storefront and checkout. Both payment methods keep working at checkout.
SYMPTOM
The server returns HTTP 200 with a completely empty body (0 bytes). With WP_DEBUG and WP_DEBUG_LOG enabled, no fatal error, memory error or warning is logged for these requests, and the host’s PHP error log shows nothing either. So it looks like execution is being stopped silently (exit/die, or an output buffer being discarded) rather than a crash.HOW WE ISOLATED IT (staging, Health Check troubleshooting mode)
- All plugins disabled: the editor loads.
- WooCommerce + PayPal Payments only: the editor loads.
- Re-enabled our other plugins one by one: the editor still loads.
- Enabled Latitude Interest Free Gateway as well: blank page.
- With the same set active, disabling only PayPal Payments OR only Latitude makes the editor load again.
So the blank screen only happens when PayPal Payments and Latitude are active together. Neither causes it on its own.
TEMPORARY WORKAROUND
We added a small must-use plugin that filtersoption_active_pluginsso Latitude isn’t loaded on post.php / post-new.php (non-WooCommerce post types), customize.php, widgets.php and site-editor.php. With that in place every affected screen loads normally and both gateways still work at checkout. That confirms the conflict happens while these screens are being rendered.QUESTIONS
- Is this a known conflict? Is a fix planned?
- Is there a PayPal Payments setting or filter we could use to stop the code that conflicts from running on block editor screens, so we can remove our workaround?
- Is there anything you’d like us to capture (e.g. a specific debug setting or trace) to help pin down where execution stops?
We can share the WooCommerce System Status Report privately if needed. We’re reporting this to Latitude as well.
Thanks for your help!
You must be logged in to reply to this topic.