# Default Post **URL:** \ **Category:** Elements CMS\ **Created:** [December 1, 2025, 12:44pm UTC](https://forums.realmacsoftware.com/t/default-post/52896 "2025-12-01T12:44:51Z")\ **Posts on this page:** 7\ **Page:** 1
**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 1, 2025, 12:44pm UTC](https://forums.realmacsoftware.com/t/default-post/52896/1 "2025-12-01T12:44:51Z")
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, 9:58am UTC](https://forums.realmacsoftware.com/t/default-post/52896/2 "2025-12-02T09:58:23Z")
The reason we do this is that if you preview the individual post page locally, by pressing command-P while on that page in Elements, you’d otherwise get an “Item not found” message. This approach ensures you can always preview an individual post page locally without running into that issue. Hope that makes sense 🙂 ---
**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, 10:14am UTC](https://forums.realmacsoftware.com/t/default-post/52896/3 "2025-12-02T10:14:43Z")
This has sparked a big discussion here: > [@BUGS in Elements CMS Build 1.5.5](https://forums.realmacsoftware.com/t/bugs-in-elements-cms-build-1-5-5/52855): > > 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 … So maybe you should change it after all? It’s not good if the preview differs from the website. ---
**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:30am UTC](https://forums.realmacsoftware.com/t/default-post/52896/4 "2025-12-02T10:30:30Z")
I think it’s worse if you preview an individual post page locally and always see an error. ---
**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, 10:48am UTC](https://forums.realmacsoftware.com/t/default-post/52896/5 "2025-12-02T10:48:09Z")
I think it’s the other way around. Using the first one alphabetically as the default would be very clever, then it could be customized accordingly. This should also be the case on the website. Or could a default be defined? ---
**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, 11:02am UTC](https://forums.realmacsoftware.com/t/default-post/52896/6 "2025-12-02T11:02:11Z")
> [@Ulrich](#): > > This should also be the case on the website. So if I have an individual post page on my website that’s meant to display a single blog post, you’re suggesting it should automatically fall back to showing the first post if the requested one can’t be found? Just making sure I’m understanding your proposal correctly 🙂 Here’s the reasoning behind the current behaviour: a single post page at `/post` is designed to show one item from a collection, identified by the `?item=slug` query parameter. **When previewing `/post` locally in Elements** , the CMS loads the _first_ item in the collection automatically — this ensures you can preview and design the post layout without there needing to be a specific item defined. It’s especially useful when pressing Command-P to preview the page directly. - Visiting `my-website.com/post?item=my-post` correctly loads the `my-post` item. - Visiting `my-website.com/post?item=a-post-that-doesnt-exist` shows “item not found” — because it doesn’t exist in the collection. - Visiting `my-website.com/post` also shows “item not found”, since no `item` parameter is provided. I don’t believe any of these scenarios justify automatically displaying a default post. If you feel strongly that this behaviour should be different, I’d love to hear more about why and exactly how you think it should work instead 🙂 ---
**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, 11:52am UTC](https://forums.realmacsoftware.com/t/default-post/52896/7 "2025-12-02T11:52:58Z")
For pages that don’t exist, the HTML error 404 _page not found_ is usually returned. This gives me the option to create a custom error page. If the wrong post, or no post at all, is accessed, I only get the page with the text _No item found_ (It could be that I saved a link to an article that no longer exists…) This isn’t ideal for the visitor. It would be better if I were then taken to a page that helps me. How could this be implemented in Elements? - If no matching or correct article is found, the first article is displayed. This could include information on what I, as the user, can do… - **Better** : I have the option to define an error page. (This could then also be a ‘standard’ post.) Currently, I solve this using a rule in the `.htaccess` or `web.config` file. This isn’t a problem for me as a technical expert, but it might be for other website developers? The behavior in the preview is fine as it is and doesn’t need to be changed. Please don’t misunderstand, this isn’t a big issue, but it did cause some confusion, and it took me also a while to understand the error message from Pegasus. Thanks for taking the time to think about it.