Yoast SEO breaks form layout on Gravity Forms with WordPress 6.9

[Digitalspirit73]

• I've read and understood the contribution guidelines.
• I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened

To Reproduce

Step-by-step reproduction instructions

1. WordPress 6.9
2. Gravity Forms - breaks layout, shows Honeypot
3. Disabling Yoast reverts issue

Expected results

1. Gravity Forms display as per 6.8.3

Actual results

1. Form layout a mess and showing hidden honeypot field

Screenshots, screen recording, code snippet

If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.

Broken layout

How it should look (with Yoast disabled):

Technical info

• If relevant, which editor is affected (or editors):

• Block Editor
• Gutenberg Editor
• Elementor Editor
• Classic Editor
• Other: Custom pages

• Which browser is affected (or browsers):

• [ x] Chrome
• [ x] Firefox
• Safari
• Other: Edge, Brave

Used versions

• Device you are using: PC
• Operating system: Windows 10/11
• PHP version: 8.3.27
• WordPress version: 6.9
• WordPress Theme: Responsive Pro
• Yoast SEO version: Latest
• Gutenberg plugin version:
• Elementor plugin version:
• Classic Editor plugin version: 1.6.7
• Relevant plugins in case of a bug:

[aljeyoast]

Please inform the customer of conversation # 1337627 when this conversation has been closed.

[aljeyoast]

Please inform the customer of conversation # 1338163 when this conversation has been closed.

[fbentele]

This is also the case for NinjaForms based forms. The stylesheets for this 3rd-party plugin (NinjaForms) are not being loaded, if Yoast is active (WP 6.9, Yoast 26.5). I was not able to find a workaround or the causing code.

[YBOP84]

It's a big issue affecting numerous installations.

For Gravity Forms users this is a hack, forcing the CSS files to be loaded.

`
add_filter( 'gform_disable_css', '__return_false', 1 );
add_filter( 'gform_disable_form_theme_css', '__return_false', 1 );
add_filter( 'gform_disable_standard_styles', '__return_false', 1 );

function force_gravityforms_styles() {
    if ( is_admin() ) {
        return;
    }

    if ( ! class_exists( 'GFCommon' ) || ! class_exists( 'GFForms' ) ) {
        return;
    }

    wp_enqueue_style(
        'gf-basic',
        GFCommon::get_base_url() . '/assets/css/dist/basic.min.css',
        [],
        GFForms::$version
    );

    wp_enqueue_style(
        'gf-theme',
        GFCommon::get_base_url() . '/assets/css/dist/theme.min.css',
        [ 'gf-basic' ],
        GFForms::$version
    );
}
add_action( 'wp_enqueue_scripts', 'force_gravityforms_styles', 20 );`

[maybellyne]

Please inform the customer of conversation # 1337642 when this conversation has been closed.

[josevarghese]

Hi @fbentele, @Digitalspirit73 and @YBOP84

Are you seeing any console errors when this occurs? Also, have you tried to check whether the filter mentioned over here helps to fix the issue or not?

add_filter( 'should_load_separate_core_block_assets', '__return_false', 100 );

[Digitalspirit73]

Can confirm adding below to functions.php resolves the issue:

add_filter( 'should_load_separate_core_block_assets', '__return_false', 100 );

[fbentele]

i can also confirm, this works and solves the ninjaforms issue on my site!

[maybellyne]

+1 https://wordpress.org/support/topic/v26-5-issue-with-wp-forms-and-livemesh/

[maybellyne]

+1 https://wordpress.org/support/topic/after-update-to-wp-6-9-yoast-seo-get-conflict-with-gravity-form/

[smdev0925]

Confirmed this resolves issues with both Livemesh and WPForms.

[enricobattocchi]

Hello everyone, we haven't been able to reproduce the issue so far with any of the plugin that have been mentioned. This probably means that there is some other factor needed to trigger the conflict, such as a caching solution, or some kind of theme (it's less likely that some other plugin is involved, since disabling that would solve that issue and some report would mention that).
We're committed to investigate deeply to find a solution since the should_load_separate_core_block_assets filter is just a temporary workaround.
Is there anyone that can provide further info about their setup, or even access to a staging copy?
Thanks for all the help.

[fbentele]

@enricobattocchi we experienced it on multiple sites we take care of for our clients. i can send you a temporary account for one of our staging sites. can you provide me a direct messaging channel so I can send you the credentials?

[enricobattocchi]

Thanks! You can write at enrico@yoast.com if email is fine for you