• As of today 6.9.4 has been released and the underlying issue does not appear to be resolved. Many assert that the issue is actually with Yoast ref. https://github.com/Yoast/wordpress-seo/issues/22788 but Yoast is denying that.

    For me personally when Yoast is enabled with 6.9.x there are multiple frontend issues, namely with Gravity Forms (for me), but also with Slide Anything and other notable plugins.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Weston Ruter

    (@westonruter)

    Another couple fixes to the CSS cascade are planned to land in 7.0. I’m planning to commit this pull request which will be part of 7.0-beta5: https://github.com/WordPress/wordpress-develop/pull/10875

    Hopefully it addresses the issue for you. If you can test 7.0-beta5 that would be helpful.

    Otherwise, if your theme continues to be incompatible with loading block styles on demand, refer to these paragraphs in the 6.9 performance field guide.

    Thread Starter guyhaines

    (@guyhaines)

    Thanks your plugin is a huge help. I have 100’s a custom classic themes from over the years and seems like half are affected. Just weird that Yoast seems to be the only culprit.

    +1. I’ve recently upgraded to 6.9.4 in a classic theme, and I realized inline styles were completely gone.
    I’ve been trying to debug WP core to understand why, but it’s quite a rabbit hole, the further I’ve got is this early return that probably breaks the original performance feature.

    function wp_finalize_template_enhancement_output_buffer( string $output, int $phase ): string {
    // When the output is being cleaned (e.g. pending template is replaced with error page), do not send it through the filter.
    if ( ( $phase & PHP_OUTPUT_HANDLER_CLEAN ) !== 0 ) {
    error_log('--------------------------------');
    error_log('phase: ' . $phase);
    error_log( PHP_OUTPUT_HANDLER_CLEAN );
    error_log('--------------------------------');
    return $output;
    }

    Where I get a phase = 11, if that makes sense. PHP_OUTPUT_HANDLER_CLEAN = 2

    Thank you Weston for the hard work.

    P.S. After reading the previous comments mentioning Yoast, I can also confirm that deactivating Yoast on the site actually works! :0

    • This reply was modified 2 months, 1 week ago by furi3r. Reason: news on the bug

    Also in my environment, uninstalling Yoast SEO resolved the display issues with Firelight Lightbox (formerly Easy FancyBox).
    Currently, I’m using Rank Math SEO as a replacement (it has an import function from Yoast).

    Therefore, Load Combined Core Block Assets is no longer necessary. Thank you very much for your help during this short time.

    Plugin Author Weston Ruter

    (@westonruter)

    @furi3r oh, just seeing your comment about the output buffering in combination with Yoast. I bet there is a conflict with the output buffering, where Yoast should actually be leveraging the new template enhancement output buffer instead of (potentially) doing their own output buffering.

    I’ll have to follow up on this.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.