# BUGS in Elements CMS Build 1.5.5 **URL:** \ **Category:** Elements CMS\ **Created:** [November 29, 2025, 12:09pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855 "2025-11-29T12:09:47Z")\ **Posts on this page:** 20\ **Page:** 1
**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:** [November 29, 2025, 12:09pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/1 "2025-11-29T12:09:47Z")
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** : ```auto {{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: ```auto {{ item.title }} - {{ item.date_published }} - {{ item.tags }} ``` This normally works without issues. However, when spacing is used in a filtered Twig expression such as: ```auto {{ 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: ```auto date: published: "2022-11-15" modified: "2024-02-10" ``` It still loads without errors, but when I try to output: ```auto {{ 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: ```auto 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: 1. **Related Items fail after publishing** (only “No item found” online). 2. **German date formatting breaks** in Collection Items. 3. **Twig spacing produces syntax errors** when used with filters. 4. **Nested YAML** **date:** **frontmatter no longer works** , always outputting today’s date. * * * ---
**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\ **Post date:** [November 29, 2025, 1:07pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/2 "2025-11-29T13:07:09Z")
Did not have extra spaces… can’t speak to that… My date is working fine ———— Question 🙋‍♂️ for you… how do you use related items? I finally got the list to show… What do you do with it? I had wanted to find related songs on my site… How do I program that? ---
**Author:** ![Ulrich](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ulrich/32/29764_2.png) [@Ulrich](https://forums.realmacsoftware.com/u/Ulrich)\ **Post date:** [November 29, 2025, 7:01pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/3 "2025-11-29T19:01:03Z")
#### 1. Related Items seems to work, look here, `Re-Published All Files` with Elements 1.5.5 > **[Aktuelles | CORNROW](https://www.cornrow.de/artikel/herr-grun-zieht-nach-lich)** > > Aktuelles - CORNROW Curly Coated Retriever, gesunde, typische Hunde-Welpen aus liebevoller Zucht. Jetzt mehr über unsere Welpen erfahren! ![image](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/a/4/a47f667d8641ef8e2bcd84d61f8ef4ec684447c5.png) #### 2. German date formatting breaks in Collection Items seems to work also, look here > **[Aktuelles | CORNROW](https://www.cornrow.de)** > > Aktuelles - CORNROW Curly Coated Retriever, gesunde, typische Hunde-Welpen aus liebevoller Zucht. Jetzt mehr über unsere Welpen erfahren! #### 3. Twig spacing syntax causes errors sorry - but no: ![image](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/d/5/d5dd02b3e2a46da0384c9a9cbf54beb67c126837.png) #### 4. YAML frontmatter never used this - should i Es tut mir wirklich leid, dass es bei mir alles zu funktionieren scheint und bei Dir nicht. Und es liegt auch nicht daran, dass ich IIS nutze, denn ich habe mir für Tests eine Apache24 Instanz installiert, die ich lokal per http erreichen kann, hier funktioniert es ebenfalls. Gerne helfe ich Dir, melde Dich. ---
**Author:** ![curlypaws](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/curlypaws/32/3964_2.png) [@curlypaws](https://forums.realmacsoftware.com/u/curlypaws)\ **Post date:** [November 30, 2025, 12:00am UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/4 "2025-11-30T00:00:15Z")
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. ---
**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:** [November 30, 2025, 11:10am UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/5 "2025-11-30T11:10:24Z")
> [@MichaelDroste](#): > > Question 🙋‍♂️ 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. 😉 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. ---
**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\ **Post date:** [November 30, 2025, 3:30pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/6 "2025-11-30T15:30:47Z")
Thank you for the detailed response… clever using the authors field… ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [December 1, 2025, 8:42am UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/7 "2025-12-01T08:42:14Z")
> [@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. > [@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. > [@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. ---
**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:** [December 1, 2025, 10:44pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/8 "2025-12-01T22:44:54Z")
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”** ---
**Author:** ![Ulrich](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ulrich/32/29764_2.png) [@Ulrich](https://forums.realmacsoftware.com/u/Ulrich)\ **Post date:** [December 2, 2025, 7:05am UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/9 "2025-12-02T07:05:33Z")
Point 1 has a new Thread: > [@Default Post](https://forums.realmacsoftware.com/t/default-post/52896): > > 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. ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [December 2, 2025, 10:01am UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/10 "2025-12-02T10:01:04Z")
> [@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? > [@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 🙂 ---
**Author:** ![Jupeman](https://avatars.discourse-cdn.com/v4/letter/j/67e7ee/32.png) [@Jupeman](https://forums.realmacsoftware.com/u/Jupeman)\ **Post date:** [December 2, 2025, 4:23pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/11 "2025-12-02T16:23:14Z")
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. ---
**Author:** ![Ulrich](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ulrich/32/29764_2.png) [@Ulrich](https://forums.realmacsoftware.com/u/Ulrich)\ **Post date:** [December 2, 2025, 5:59pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/12 "2025-12-02T17:59:45Z")
The _Item not found_ issue has a new thread: > [@Default Post](https://forums.realmacsoftware.com/t/default-post/52896): > > 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. ---
**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:** [December 4, 2025, 8:40pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/13 "2025-12-04T20:40:19Z")
@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.” ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [December 4, 2025, 10:54pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/14 "2025-12-04T22:54:40Z")
@Pegasus Sorry for the delay, we’ll dig into this tomorrow for you! ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [December 5, 2025, 12:49pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/15 "2025-12-05T12:49:10Z")
Hi @Pegasus I just replied to your email, but wanted to post here as well for transparency and information to anyone else reading this thread 🙂 > In the local preview I can see the related items, but online at [https://www.nurkochen.de/kochblog/test/](https://www.nurkochen.de/kochblog/test/) it only shows **“No item found”**. That’s because the Item on the “test” page is set to use a Collection, which means it requires an `?item=slug` query parameter. If you visit [test](https://www.nurkochen.de/kochblog/test/?item=a0023_kochen-ist-leidenschaft) you’ll see everything working correctly, including the related items. **Why does this work locally but not when published?** In local preview, if no `?item=slug` is present, Elements automatically loads the first item in the Collection so you can preview the individual post template without needing to navigate from the main listing page. This fallback only happens locally, not on the published site — which is why the live page shows “No item found” unless a valid `?item=slug` is provided. So in short: this behaviour is expected. Do let me know if you have any more questions 🙂 > The **related item** on the pages in the directory [www.kaufsonntag.de/international/belgien/](http://www.kaufsonntag.de/international/belgien/) > _works correctly_. But the **related item** on the pages in [www.kaufsonntag.de/baederregelung-verordnung/bayern/](http://www.kaufsonntag.de/baederregelung-verordnung/bayern/) _does not work_. Neither related items component is configured correctly. They’re currently set to fetch related items by author, but you don’t have an authors folder setup. To use author-based relationships, you’d need an `authors` folder at the same level as each collection. I’d recommend switching the components to fetch related items by tags instead, that way you can just add the appropriate tag(s) to each post and it will work as expected. The reason one of the pages may have seemed to work before is due to a previous bug in the Related Items component where it returned items even when none were found. That bug has now been fixed, which is likely where the confusion comes from. In short: related items are behaving correctly once the component is configured properly. ---
**Author:** ![curlypaws](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/curlypaws/32/3964_2.png) [@curlypaws](https://forums.realmacsoftware.com/u/curlypaws)\ **Post date:** [December 5, 2025, 3:57pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/16 "2025-12-05T15:57:28Z")
Hi Ben, it would be really useful to have some examples of how to configure a blog to use related items with authors as well as with tags as it isn’t too clear to me how to do this (I’ve been trying to set them up for authors on a test site and can’t figure out how to make it work). ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [December 5, 2025, 3:58pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/17 "2025-12-05T15:58:43Z")
We’re putting together a new CMS Project that is more advanced than the microblog example we currently have available… stay tuned for that! ---
**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:** [December 5, 2025, 4:06pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/18 "2025-12-05T16:06:58Z")
@ben thanks for the feedback and your explanations. However, I am _very_ sure there is a bug here. I spent the entire afternoon today setting up very simple test projects… and on pages where it initially worked, the related items stopped working as soon as I added new pages. I don’t yet know exactly how or when the issue occurs, but I think I’m getting closer to identifying it. I’ll get back to you as soon as I’ve found the cause of the problem. ---
**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:** [December 6, 2025, 10:30am UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/19 "2025-12-06T10:30:29Z")
@dan @ben YEAH! I think I finally figured it out… It seems to be a **Markdown parser issue** , specifically related to how the Markdown files are named. I tested several Markdown files with different file names. Normally, when you create a new Markdown page via the Elements tool (“Create a new Markdown page”), the files are generated like this: ```auto 2025-month-day_title.md ``` However, when Markdown files are named simply: ```auto one.md two.md three.md four.md five.md ``` …the **related items feature does not work** , even though all parameters in the frontmatter are identical. But as soon as the Markdown files are renamed to something like: ```auto site-one.md site-two.md site-three.md site-four.md site-five.md ``` …the related item functionality works again. So it looks like the parser has trouble when the file name contains **no hyphen or underscore before the first segment** , which many people might run into if they name their blog articles only after the title. As a result, this can cause issues when generating related items, because the system expects a certain naming pattern before the first “-” or “\_”. Attached is a Markdown file overview from my test project. **Red = related items do NOT work** **Green = works** ![Bildschirmfoto 2025-12-06 um 10.57.12](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/7/a/7a404eb7d057652bdcb454b098785081862273fe.png) It looks like the Markdown parser always commits to only one “version.” I tested this by deleting all Markdown files. After uploading them again, all the files that were previously marked red suddenly worked, and the green ones stopped working. ---
**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\ **Post date:** [December 6, 2025, 2:11pm UTC](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855/20 "2025-12-06T14:11:13Z")
Trying to understand… _Use 00001_ 00001name.md **Or** _Don’t use 00001_ name.md Thanx 🙂 Mike [Next page](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855.md?page=2)