Recurring output buffering conflicts between LiteSpeed Cache and WordPress core/
-
Hello,
We are encountering recurring output buffering issues with LiteSpeed Cache that are causing critical errors on our WordPress site. Below are the specific errors we have identified:
- Yoast SEO (
addon-update-watcher.php
):- File:
/wp-content/plugins/wordpress-seo/src/integrations/watchers/addon-update-watcher.php
- Line: 197
- Error:
LiteSpeed\Root::cls(): Cannot use output buffering in output buffering display handlers
.
- File:
- Yoast SEO (
auto-update-watcher.php
):- File:
/wp-content/plugins/wordpress-seo/src/integrations/watchers/auto-update-watcher.php
- Line: 12
- Error:
LiteSpeed\Root::cls(): Cannot use output buffering in output buffering display handlers
.
- File:
- WordPress Core (
ajax-actions.php
):- File:
/wp-admin/includes/ajax-actions.php
- Line: 4577
- Error:
LiteSpeed\Root::cls(): Cannot use output buffering in output buffering display handlers
.
- File:
- WooCommerce (
class-woocommerce.php
):- File:
/wp-content/plugins/woocommerce/includes/class-woocommerce.php
- Line: 407
- Error:
LiteSpeed\Root::cls(): Cannot use output buffering in output buffering display handlers
.
- File:
- Yoast SEO (
yoast-tools-page-conditional.php
):- File:
/wp-content/plugins/wordpress-seo/src/conditionals/yoast-tools-page-conditional.php
- Line: 15
- Error:
LiteSpeed\Root::cls(): Cannot use output buffering in output buffering display handlers
.
- File:
- Issues with
wp-login.php
and/wp-admin
:- Output buffering conflicts are affecting the functionality of these pages, causing errors during login and backend actions.
These errors appear to stem from conflicts between LiteSpeed Cache’s output buffering functionality and processes in WordPress Core, Yoast SEO, and WooCommerce.
Could you provide guidance or a fix for these issues?
Thank you for your assistance.
- Yoast SEO (
Viewing 8 replies - 1 through 8 (of 8 total)
Viewing 8 replies - 1 through 8 (of 8 total)
- You must be logged in to reply to this topic.