ItzCookie

Very weird. I’ve tried “color” with different combinations targeting dd or dt, and neither of them worked ??

I did table dt, table td dt, table > td > dt etc. Neither of them worked. Probably related to mPDF…

dl, dd and dt are used for product meta data and variation data. For example: product color, brand etc.

Non of them are targeted by CSS. I have found a workaround, so you can close this, but for the future, this somehow should be resolved.

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 ??

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.

Hello,

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

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

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.

I have just reported a similar issue. It happens with WP 5.7. Downgraded to 5.6.2 and it fixed that. Waiting a reply from yoast support

I have just reported a similar issue. It happens with WP 5.7. Downgraded to 5.6.2 and it fixed that. Waiting a reply from yoast support

This is one the best comments i’ve read in the review section. I could not agree more that this will bring a huge mess for many clients and developers if it will be merged into he core.
And one of the best arguments that you have given was that this was probably developed for millennials.
I cant even imagine doing so many actions for a simple article, yet to work and code with it. Ive been developing with WP for over 8 years now and now this comes out? Please, leave it as a plugin. I dont want to face the incompability for every client we have

You removed wpdb->prepare which is unsafe. With “prepare” you set the query to be safely executed. I’m not going to use this method and neither should you.

Thanks, all good now!

Hi, Marcin,

All good now, thanks! Glad to be helpful!

Cheers!

Dear @iworks,

Thanks for the code, that did solve the issue. Will be waiting for an update ??

I’ll do that first thing in the morning. But looking from the code you posted, that gives a lot of hope to work. I’ll post the results tomorrow!