• Resolved jvmedia

    (@jvmedia)


    We noticed the following today on a site we’re working on finishing:

    Fatal error: ob_start(): Cannot use output buffering in output buffering display handlers in /nfs/c10/h06/mnt/176860/domains/clientsitetest.com/html/tristar/wp-content/plugins/woocommerce/includes/wc-template-functions.php on line 2846

    We’ve tracked down what seems to be causing the issue. On the categories that have the fatal error, within the category description we’ve got [product-search] to bring up the product search. It was working, but after a couple updates, it seems that it’s no longer compatible. When we deactivate All in One SEO, the fatal error is fixed and the page displays properly.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Unfortunately we can’t reproduce this on our end, and it seems you may not be using the latest version of WooCommerce. This is line 2846 which obviously wouldn’t cause that error: https://github.com/woocommerce/woocommerce/blob/ba517650a18f9b7f2ba47f8671b7f6d728bf3e64/includes/wc-template-functions.php#L2846

    Without more information, there’s not much of anything we can do. I’d start by disabling all plugins other than AIOSEOP and WC, and switch to the default theme and see if the behavior exists.

    If all else fails, in All in One SEO Pack, you can go to the Performance Module and disable the Force Rewrites option which should avoid the error.

    Thread Starter jvmedia

    (@jvmedia)

    Thanks for checking into it.

    Update from our end: It appears that the plugin Visual Term Descriptor (which is not one we’ve ever used before) is the culprit. With that and All In One SEO activated, the error comes up. With All In One SEO deactivated, but Visual Term Descriptor still active, the error goes away. With All In One SEO activated and Visual Term Descriptor deactivated, the error goes away. Also, we are running version 3.6.5 of WooCommerce. So perhaps there is some incompatibility there with the Visual Term Descriptor. We don’t really need that one, so we’re ditching it and problem is solved.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Thanks for the followup. I’m glad you got it working. ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal Error with Woocommerce’ is closed to new replies.