Related posts in bold after upgrade

I’m seeing the same problem. Can we get an answer on this one please?

Same problem also : https://www.randos-montblanc.com/facile/mont-lachat-chatillon.html

The font is not the same. Do you have any idea about that?

Just remove font-weight: bold !important; in related.css into the folder style of the plugin.

Yes, tonysiino is correct. Sorry for the inconvenience.

Well, I did what tonysiino suggested but the bold is still there. I just emptied the W3TC cache but still there. Where did I go wrong?

Hi editor. I still see that .yarpp-related a is still bold on your site. Perhaps editing related.css to change .yarpp-related a to {font-weight:normal !important;} will fix it for you.

Actually, I deleted all the code lines involved. Previously I made the change you suggested without any result. Maybe it’s CloudFlare, I have to purge the cache, I just don’t know.

Jeffparker firstly: thanks for your work!

Can you tell why you added this change to related.css?
Also it’s always !important…. So I cannot overwrite it.
I have to manage 37 websites that use yarpp – I will have to fix it everywhere after the update, that’s a no-go. Can you please remove it and let me choose if I want to have it bold or not?

In addition to changing from “bold” to “normal” on line 7 of /plugins/yet-another-related-posts-plugin/style/related.css, make the change on line 12 too. That worked for me.

Uploaded again the related.css file, edited line 7 and 12 with “normal” instead of “bold”, purged cache on W3TC and CloudFlare. Nothing happened. I’m clueless, I give up. I’ll wait for an update of the plugin, hopefully without bold as the default.

Hi editor. I’m still seeing the original related.css on your site. Can you check to see that you are updating the live site?

Sure, but what do I have to do? I’m using W3TC and Cloudflare, but I emptied both caches…

After 2 days, the bold has disappeared. What a mistery ??
Thanks for the suggestion to fix this.

That is strange. Glad it’s now working the way you want.

Jeff: A simple fix for this would be to allow users to disable loading related.css within their theme.

This could be as simple as a checkbox in the YARPP settings menu:

[x] Disable related.css (custom themes only)

I think this latest update broke a lot of themes, and being able to disable related.css would be an easy solution for those with custom YARPP designs. Once it’s checked, it would also prevent future updates to related.css from overwriting those custom themes again.

I attempted to dequeue “yarppRelatedCss” but for some reason it kept loading related.css.