Wrong Breadcrumbs and OG meta

Hi,

We see you have two different issues. We will respond to them below.

A. For example, the single products page is pulling a random word from the site instead of the product name (Home > Someword) instead of (Home > Product Title)

1. To clarify, you have a custom post type called Salon and Yoast is outputting the wrong item in the breadcrumb pathway. You want the title?

2. Are all your non-Yoast plugins and themes also updated?

3. If you go to SEO-Search Appearance-Breadcrumbs and scroll down there is a list of drop-down boxes. Can you confirm the right items in those drop-down boxes have been selected? If you select None does the issue resolve?

4. Can you provide a link to the issue?

5. We had another recent release. Can you confirm you are using the most recent Yoast SEO, v15.9.2? If you update, does the issue resolve?

B. The OG description is being pulled from a different custom post type too. Happens only in WP 5.7. Downgraded to 5.6.2 and the problem fixed itself so it’s definitely related to WP 5.7 and yoast not being compatible.

1. Is this happening on the same post identified in A, above or a different one?

2. If a different one, can you provide a link to it?

3. Is everything updated on the site?

4. What is the expected og:description tag you want Yoast to generate? What is the tag Yoast is showing instead?

Both of the issues are related and the error happens for the breadcrumb title and the og description (on the same page). The theme is custom coded (by me) and the issue only starts after upgrading to WP 5.7

1. I have the salon post type name outputted on the product page (on Woocommerce single template). It should be only the Woocommerce product name.
2. Yes, everything is up to date, just WP is downgraded to 5.6.2
3. No, I have just selected everything to “None” and the issue is still there.
4. No, the live site is currently on 5.6.2, so you won’t able to see the issue.
5. Yes, my current Yoast version is 15.9.2

============

1. Yes, same post as mentioned above.
2. Same post.
3. Yes, all of the plugins are up to date. Just WP is 5.6.2 currently.
4. Yoast should generate a product description (as it normally does) since it’s a woocommerce product page, but it’s actually taking the info for breacrumbs and OG tags from my post type (salons)

Note: both of the issues are related and happening on the same page.

Furthermore, I have dump’ed some data from

$output = $before . self::get_instance()->render() . $after;

The render() dump is below in the screenshot

Here’s the result. The CPT should be “product”, but for some reason it’s pulling the locations (salons) post type.

https://paste.pics/412689af8d96f3bd164a9a43a9ad9811

@sawsainis

OK! ?If you use the Yoast Helper Tool does the issue resolve? Please try the steps below:
– i. Install & activate the Yoast Test Helper plugin:?https://www.ads-software.com/plugins/yoast-test-helper/
– ii. Go to Tools -> Yoast Test
– iii. Locate the Yoast SEO section and select the “Reset indexables tables & migrations” button
– iv. Click the “SEO Data” button in the SEO->Tools section.

Hello,

No, unfortunately, these steps didn’t help. I’m still seeing both of the issues.

We use the indexables to store data. It appears that for some reason an incorrect permalink has been generated for that product. We are not sure why this is happening.

We ask that you please perform a conflict check.

Please Check for conflicts. Install the Healthcheck plugin and enable troubleshooting. Then switch to a standard theme like 2020. Does the issue resolve? NOTE: This will not affect how users see your site.

Does the issue resolve if Yoast is the only plugin active, you have whatever plugins are required to make those product pages and the theme is 2020?

It doesn’t make sense going to troubleshoot mode, because it disabled everything and switches to a default theme. Of course the problem will disappear because all of the custom post types are missing. I’m not sure how this can help.

Even if I disable of my custom post types, the issue still there, because YOAST somehow picks the description and the breadcrumb from the database (or somewhere where it saves the data)

I’ve been coding for years on wordpress and I’m already getting frustrated because of this issue.

I think I made it clear, that this only happens when i upgrade to WP 5.7, so this is related to the newest WP core update.

I’m using plugins like ACF but just for coding.

Hi @sawsainis,

Thanks for the feedback!

We understand the frustration the issue is causing and know that the situation is upsetting. However, we are not familiar with your specific set-up or what kind of customizations are in use by it. We are also not sure what exactly has been done.

We had wanted a conflict check to be performed so as to help rule out a plugin or theme conflict has causing the issue.

Based on the reply, the issue does seem to still occur despite the elimination of most of the un-required plugins.

As a result, we expect this to be a bug. We’re actively using the bug tracking on our GitHub repository so your best next step would be to create a new issue for our developers at https://github.com/Yoast/wordpress-seo/issues/new. The Github repository is actively monitored so you can expect a reply from a developer.

You will need an account to create a new issue. If this is your first bug report, please check out: https://kb.yoast.com/kb/how-to-write-a-good-bug-report/.

You can also link back to this forum post in the issue report.

I have submitted a git request to your developers here:
https://github.com/Yoast/wordpress-seo/issues/16781

I am seeing a very similar issue in another thread here which i might think can be related:
https://github.com/Yoast/wordpress-seo/issues/16769

Let me know if I can help to solve this in any way. I’ve been coding with wordpress for over 8 years, but I’m not seeing any errors or anything, so I thought your devs will be more helpful than me digging it on my own ??

Hi,

Thanks for creating the issue on GitHub. Our developers will be taking a look and providing feedback on GitHub, so please do keep a lookout for that. We’ve also referenced and linked the other issue.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.