# Latest CMS2 Update Killed the Related Blog Posts? **URL:** \ **Category:** Elements\ **Created:** [May 22, 2026, 7:32am UTC](https://forums.realmacsoftware.com/t/latest-cms2-update-killed-the-related-blog-posts/56262 "2026-05-22T07:32:55Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Pegasus](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/pegasus/32/25035_2.png) [@Pegasus](https://forums.realmacsoftware.com/u/Pegasus)\ **Post date:** [May 22, 2026, 7:43am UTC](https://forums.realmacsoftware.com/t/latest-cms2-update-killed-the-related-blog-posts/56262/2 "2026-05-22T07:43:51Z")
I’m seeing the same issue on my side. Ben has already identified the cause. It seems to be related to different types of quotes being used in the Markdown frontmatter. At least that was the case for me. Unfortunately, it’s not very easy to spot the difference between normal quotes and smart quotes in the Elements Markdown editor. I had ChatGPT replace all the quotes in my Markdown files with normal ones, and everything is working again now. I assume there will probably be an update for this later today — or you can do what I did and have everything corrected. > [@RapidWeaver Elements 2.4.1 Now Available](https://forums.realmacsoftware.com/t/rapidweaver-elements-2-4-1-now-available/56252/13): > > I tracked this down to malformed YAML front matter in a couple of your Markdown files. One of the description fields starts with a normal double quote but ends with a smart quote, so the front matter parser cannot read it. Related Items made the issue visible because it scans the other items in the same collection to find matches, so a single malformed item can trigger the error even when viewing a different page. We’ll tighten up the parser so it can recover from this specific quote mismatch… --- _[View the full topic](https://forums.realmacsoftware.com/t/latest-cms2-update-killed-the-related-blog-posts/56262)._