wjh

We’re encountering the exact same problem. Our WP website is a multi-site install, if that helps.

Thank for your prompt attention to this matter.

Hi @maybellyne, we’re having the same problem here.

My coding skills are poor, but I’m trying to put together a fix from various sources, including official Yoast tech doc.

Google Search Console is accurately identifying our Buddypress user profiles as Profile Pages, but the Yoast plugin is identifying them as Webpages, so I’ve tried adding this code to our theme’s functions.php file:

add_filter( 'wpseo_schema_webpage', 'yoast_buddypress_fix' );
/**
 * Changes @type of Webpage Schema data.
 *
 * @param array $data Schema.org Webpage data array.
 *
 * @return array Schema.org Webpage data array.
 */
function yoast_buddypress_fix( $data ) {
    if ( ! bp_is_user() ) { // if current page is not Buddypress user profile page
        return $data;
    }

    $data['@type'] = 'ProfilePage';
    $data['mainEntity'] = 'Person';

    return $data;
}

However, this is not overriding the Yoast schema output, which still indicates that the user profile is a simple Webpage, nor is it fixing the mainEntity error.

Any help on getting this to work would be most appreciated!

• This reply was modified 2 years, 2 months ago by wjh.

@samperrow First and foremost, thank you very much for this excellent plugin!

Like other users, I of course look forward to upgrading to the major new version, whenever you get a chance to finish it 😉

Following up on @dan14’s question, just to confirm: with the new version of the plugin, in order to make preloading responsive, will we be able to specify the “media” parameter(s)?

For example:

<link rel="preload" href="bg-image.png" as="image" media="(max-width: 600px)">

[Specs on MDN Web docs]

I thank you in advance for your reply.

@pembo13

that helped, thanks

Cheers

Looks like there are no conditionals for a “physical” location?

Not a dedicated conditional tag, no: unfortunately, the plugin authors made the new URL field a sub-field of {has_location}.

As a workaround, I activated the nesting of conditional placeholders and created an EM tag called Video conference. I added this tag to all video-based events (thankfully there were only a few), and then nested the {has_tag_X} and {no_tag_X} conditional tags inside {has_location} i.e.:

{has_location}
  {has_tag_videoconference}
    <p>Video conference</p>
  {/has_tag_videoconference}
  {no_tag_videoconference}
    <p>#_LOCATIONTOWN, #_LOCATIONREGION #_LOCATIONIMAGE{25,25}</p>
  {/no_tag_videoconference}
{/has_location}
{no_location}
   <p>Venue TBD</p>
{/no_location}