• Resolved YuMyo

    (@nikho)


    Hi,

    Prevent widows on titles adds &nbps; to the Seo Yoast title and meta description output.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author pepe

    (@pputzer)

    You mean on the frontend? In which field? I just tested this on a live site and I could not find any   in the og:description tags. However, a non-breakable space should not be a problem even if it was inserted there, no?

    Thread Starter YuMyo

    (@nikho)

    Yes on the frontend side, page title and meta description in the document head.
    Yoast also applies the same values to the OG and Twitter card meta. However, I am using the wpseo_title and wpseo_metadesc filters to pass ACF values to those fields.

    Plugin Author pepe

    (@pputzer)

    It would appear that this depending on your Titles & Metas setting (and your theme of course). I have not been able to reproduce this issue with the %%title%% %%page%% %%sep%% %%sitename%% setting in Yoast SEO (neither using the Libre nor the using the Twenty Fifteen theme).

    Thread Starter YuMyo

    (@nikho)

    Yes, I think it might be related to the above filters as I got no other theme specific mods. Anyway, it doesn’t affect search and shouldn’t affect ranking as Google knows what a   is.

    Plugin Author pepe

    (@pputzer)

    Ah, it might be because in recent versions, wp-Typography also processes some ACF output filters. If you don’t want that, you can remove the filters via

    remove_filter( 'acf/format_value_for_api/type=TYPE', array( WP_Typography::get_instance(), 'process' ), 9999 );

    For ACF Pro, the filter hook would be acf/format_value/type=TYPE and TYPE should be replaced with wysiwyg, textarea or text, depending on the field type you don’t want filtered.

    Plugin Author pepe

    (@pputzer)

    Have you been able to resolve the issue?

    Thread Starter YuMyo

    (@nikho)

    @pputzer thanks for pointing out the remove_filter option. By now, I am including title in the list of the Do not process HTML elements and this solves the issue with no side effects as I am using WP Typography on a case by case basis with $typo->process( $title ); but I’ll give your snippet a spin as soon as I have more time to play with it.

    • This reply was modified 8 years, 4 months ago by YuMyo.
    Plugin Author pepe

    (@pputzer)

    Great!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Seo Yoast compatibility’ is closed to new replies.