I updated to version 1.5.5 two days ago, and since then I have noticed several bugs while using the CMS. Below is a detailed summary of all issues I have encountered. 1. Related Items no longer work The Related Items feature has stopped functioning — at least once the project is published on my server. Locally and in the Elements Preview, the related items are displayed correctly. On the live website, however, only the message appears: “No item found” So something breaks during or after publishing. 2. German date formatting breaks in Collection Items Using the German date formatting works inside a Single Post Item: {{item.date_published|format_datetime('long', 'none', locale:'de')}} But as soon as I use the exact same code inside a Blog List (Collections Item), it no longer works. So the formatting behaves differently depending on the context, which should not happen. 3. Twig spacing syntax causes errors I prefer using Twig with spacing for better readability, for example: {{ item.title }} - {{ item.date_published }} - {{ item.tags }} This normally works without issues. However, when spacing is used in a filtered Twig expression such as: {{ item.date_published | format_datetime('long', 'none', locale:'de') }} …Elements CMS throws the following error: Fatal error: Uncaught Twig\Error\SyntaxError: Unexpected character ’ in __string_template__29fef4eb506be81d2797c94c7ca71f4d at line 24. It would be extremely helpful if Twig spacing syntax could be supported consistently across all expressions. 4. YAML frontmatter date: no longer works The nested YAML structure below used to work earlier in my projects: date: published: "2022-11-15" modified: "2024-02-10" It still loads without errors, but when I try to output: {{ item.date.published }} …the website always displays the current date, not the value that is actually written in the frontmatter. Because of that, I had to switch back to the old approach: date_published: "2022-11-15" date_modified: "2024-02-10" I would appreciate feedback on this. This nested format must have worked before, otherwise I wouldn’t have used it in my projects. Summary Here are the four issues again in short: Related Items fail after publishing (only “No item found” online). German date formatting breaks in Collection Items. Twig spacing produces syntax errors when used with filters. Nested YAML date: frontmatter no longer works , always outputting today’s date.

How do I link from a related item to the Post concerned? I’ve tried using {{item.url}} as the link within the Related items {{item.title}} but it doesn’t seem to work (at least previewing in the browser). The link it generates looks correct though.

[image] MichaelDroste: Question :man_raising_hand: for you… how do you use related items? To be honest, I’m not fully sure yet how to use the related items in the most meaningful way — at least not as long as I can’t get them to work reliably. ^^ I’m probably not using them the way @ben originally intended. Especially the “author” field: I’m using it differently than it was designed. Because let’s be honest — as long as there’s no external online access and most projects only have one author anyway, the author field isn’t really needed in its classic sense. Since the current Elements CMS setup allows filtering by tags, but not by categories, I simply repurposed the author field and turned it into my own category system. :wink: For your example, this would mean you could have “authors” like Rock & Pop, Classic Music, Jazz, etc. This gives me additional and more flexible filtering options — even though the possibilities with related items are currently still quite limited. Personally, I prefer using Collection Items, because the built-in filtering options give you much more control over what gets displayed. Maybe the related items feature will be expanded in the future and allow filtering by categories as well. Let’s wait and see … but first I need to fix my own related-items problem — which works randomly at best, and currently mostly doesn’t work.

Thank you for the detailed response… clever using the authors field…

[image] Pegasus: But as soon as I use the exact same code inside a Blog List (Collections Item), it no longer works. What no longer works, do you have an error being displayed? The CMS uses the same twig installation across all components, so it seems odd it would work on one page and not another. [image] Pegasus: Uncaught Twig\Error\SyntaxError: Unexpected character ’ I don’t think this is an issue with adding spaces, more that when you add a space after a single quote Elements is converting that to a “pretty quote”, which is an invalid character. The fix is to delete the curly quote and re-type it as a plain ASCII ' so Twig can parse it correctly. I will see if we can do some checking in the component/CMS to convert these automatically, hopefully we can improve this in the near future. [image] Pegasus: This nested format must have worked before, otherwise I wouldn’t have used it in my projects. I would have to investigate this one, but yes, you should have access to all the custom frontmatter.

The issues in points 2 and 3 are actually caused by the wrong ASCII ’ character — it’s a pretty sneaky problem. That means: once I replace the incorrect “ASCII ’” after copying or pasting it with the correct character, everything works as expected. Thanks for pointing that out. Regarding point 4: I would really appreciate it if this could be fixed again in one of the upcoming updates. That only leaves point 1: There must be something “buggy” here. I simply cannot get the related items to work anymore. No matter how simple I make the frontmatter … locally, in the preview, all related items are displayed correctly. But as soon as I publish the page, I only get: “No item found”

Point 1 has a new Thread: [image] Default Post card_index_dividersElements CMS Hi @ben when I preview the URL /post/ directly in the microblog, I get the first post alphabetically. However, when I view it on my web server, I get the message “No item found”. This is confusing and should behave the same way. Thanks in advance.

[image] Pegasus: Regarding point 4: I would really appreciate it if this could be fixed again in one of the upcoming updates. I didn’t understand what the issue was with point 4. Can you expand on that one? [image] Pegasus: There must be something “buggy” here. I simply cannot get the related items to work anymore. No matter how simple I make the frontmatter … locally, in the preview, all related items are displayed correctly. But as soon as I publish the page, I only get: “No item found” I would need to see ideally a project, or at least a live URL, before I could even guess at what’s going on here :slight_smile:

Something changed in an early 1.5.x version prior to 1.5.3 that gave me “No item found” on related items. My fix was to update my nginx server block. I have not re-published my site since 1.5.3 to see if anything else has changed that might have broken my nginx server block, but if you run nginx let me know and I’ll share what I have.

The Item not found issue has a new thread: [image] Default Post card_index_dividersElements CMS Hi @ben when I preview the URL /post/ directly in the microblog, I get the first post alphabetically. However, when I view it on my web server, I get the message “No item found”. This is confusing and should behave the same way. Thanks in advance.

@ben Is there any update on this? Did my email with the link to the project arrive, and were you able to identify the issue? Unfortunately, I’m now also experiencing a problem where newly added CMS items in existing projects are not being displayed online. This mainly affects newly created pages. As mentioned before, everything looks normal in the preview — but as soon as I publish the project, it only shows “item not found.”

BUGS in Elements CMS Build 1.5.5

RapidWeaver Elements CMS

Ulrich (Ulrich C. Thiess) December 2, 2025, 5:59pm 12

The Item not found issue has a new thread: