# CMS update coming next week…

**URL:** <https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676>\
**Category:** Elements CMS\
**Created:** [August 11, 2025, 9:27am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676 "2025-08-11T09:27:02Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**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:** [August 11, 2025, 9:27am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/1 "2025-08-11T09:27:02Z")

</div>

Hey All,

I just wanted to let you know that we’re working hard on fixing up all the reported CMS issues, and we plan to push out an update sometime next week.

Keep the CMS feedback coming, it’s all been really helpful and encouraging so far 😊

Can’t wait to show you all what we got cookin’

Cheers,  
Dan

---

<div class="post-metadata">

**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:** [August 11, 2025, 10:08am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/2 "2025-08-11T10:08:24Z")

</div>

**Is the following on your roadmap for an upcoming update?**

1. **Automatic Placeholder Images**  
Ability to use a default/placeholder image—e.g.:  
`{{ item.image.src | default: '/images/placeholder.webp' }}`  
…when `item.image.src` is not set in the Markdown frontmatter.

2. **Count Items in a Collection**  
Ability to output the number of, for example, events within a collection, like:  
`{{ collections.events|length }}`

---

<div class="post-metadata">

**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:** [August 11, 2025, 10:17am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/3 "2025-08-11T10:17:48Z")

</div>

Okay, here we go…

1. No, this is not on our list right now… and I’m not sure why this would be helpful as you’d need to replace before you publish anyway? Unless I’ve got the wrong end of the stick 😆
2. You want to the return the number of items in a collection? So if I had 5 markdown files in a collection, you’d want to return that as a number?

Let me know your thoughts 🙂

---

<div class="post-metadata">

**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:** [August 11, 2025, 10:47am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/4 "2025-08-11T10:47:44Z")

</div>

**1. Store Images / Placeholder Logic**

Let’s say I’m building a website for a business that has multiple locations across the country. For each location, I want to display a photo. However, sometimes I might not have an up-to-date photo for a particular branch.

In that case, I’ll leave the `image:` field empty in the corresponding Markdown file for that location.

If the field is empty, the site should display a default placeholder image that I’ve chosen.

Or let’s say I have a blog, but I’m too lazy right now to find or create an image. Still, I want to publish my blog post right away…

In that case, I just leave the image: field blank, and a placeholder image will be displayed automatically.

* * *

**2. Counting Stores by Tags**

Still talking about those business locations: I use tags for each branch like “very friendly”, “very clean”, or “fast service”.

If I create, say, 50 Markdown files (one per branch), not every location will have all the same tags.

Now, I want to automatically display the number of branches that are tagged as “very friendly”, and how many are tagged as “very clean”.

For example: “There are (number) of stores that are ‘very friendly’ and (number) that are ‘very clean’.”

And, if I later add a 51st, 52nd, or 53rd branch, this count should automatically update to reflect the new data.

---

<div class="post-metadata">

**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:** [August 11, 2025, 11:05am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/5 "2025-08-11T11:05:29Z")

</div>

> [@Pegasus](#):
>
> In that case, I’ll leave the `image:` field empty in the corresponding Markdown file for that location.

We could add support for that… or you could just add your own placeholder to the project: `image: image/placeholder.jpg`

I’m pretty sure whatever placeholder we added, wouldn’t be good for everyone. Now, I’m not saying we won’t add this, but it feels like something that’s not required (yet). Will give it some more thought. 🤔

> [@Pegasus](#):
>
> If I create, say, 50 Markdown files (one per branch), not every location will have all the same tags.

I think you want a tag cloud… with the number of times they are used in the tag? so they display something like this: Friendly (23), Clean (52), Fast Service (38)

Or were you after a computed value based on the number of tags selected. So if I selected “Friendly (5)” and Clean (10)” you would show just the stores that matched those tags (along with the number)?

If I’m still wrong, perhaps you have an example site, or an image of what you’re tying to do?

---

<div class="post-metadata">

**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:** [August 11, 2025, 11:44am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/6 "2025-08-11T11:44:22Z")

</div>

> [@dan](#):
>
> We could add support for that… or you could just add your own placeholder to the project: `image: image/placeholder.jpg`
> 
> I’m pretty sure whatever placeholder we added, wouldn’t be good for everyone. Now, I’m not saying we won’t add this, but it feels like something that’s not required (yet). Will give it some more thought. 🤔

No, I think we’re misunderstanding each other on this point.

What I mean is the function in the current Image Component ({{ item.image.src | default: ‘/images/placeholder.webp’ }}) isn’t working.

 ![Bildschirmfoto 2025-08-11 um 13.39.22](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/9/f/9f915b0feecdf8cf68c9f4125accce6d05ca52b2.png)

I’ve already placed my own placeholder image in the Resources folder.  
Now, I’d like to use the function {{ item.image.src | default: ‘/images/placeholder.webp’ }} to point to my own placeholder image.

> [@dan](#):
>
> I think you want a tag cloud… with the number of times they are used in the tag? so they display something like this: Friendly (23), Clean (52), Fast Service (38)
> 
> Or were you after a computed value based on the number of tags selected. So if I selected “Friendly (5)” and Clean (10)” you would show just the stores that matched those tags (along with the number)?
> 
> If I’m still wrong, perhaps you have an example site, or an image of what you’re tying to do?

yes. in this case, i’m interested in both options ^^

---

<div class="post-metadata">

**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:** [August 11, 2025, 12:26pm UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/7 "2025-08-11T12:26:53Z")

</div>

> [@Pegasus](#):
>
> I’ve already placed my own placeholder image in the Resources folder.  
> Now, I’d like to use the function {{ item.image.src | default: ‘/images/placeholder.webp’ }} to point to my own placeholder image.

Ah no, that’s not going to work or be supported. However, you’d probably be able to do it with the “Conditional” Component @ben has built 😉

Essentially, you’ll be able to do things like “If no image exists, display this instead”.

We’ll be releasing this component later once we have the basics of the CMS rock solid!

---

<div class="post-metadata">

**Author:** ![PLM](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/plm/32/31094_2.png) [@PLM](https://forums.realmacsoftware.com/u/PLM)\
**Post date:** [August 11, 2025, 12:36pm UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/8 "2025-08-11T12:36:59Z")

</div>

Don’t forget the other parts of Elements …

---

<div class="post-metadata">

**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:** [August 11, 2025, 1:23pm UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/9 "2025-08-11T13:23:28Z")

</div>

Don’t worry, the main app is also getting updates. We’re working on ALL the things, ALL the time 😆

---

<div class="post-metadata">

**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\
**Post date:** [August 21, 2025, 1:43am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/10 "2025-08-21T01:43:01Z")

</div>

@dan Any news on a fix for the “Load More” feature not working on pages other than the home page?

This is the one thing holding me back from publishing updates to a couple of sites.

---

<div class="post-metadata">

**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:** [August 21, 2025, 6:52am UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/11 "2025-08-21T06:52:52Z")

</div>

I started looking at the issue yesterday, hoping to have it fixed this week (no promises as the fix is more complicated than I had hoped!).

---

<div class="post-metadata">

**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\
**Post date:** [August 21, 2025, 3:21pm UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/12 "2025-08-21T15:21:43Z")

</div>

I’ll keep my fingers crossed!

---

<div class="post-metadata">

**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:** [August 21, 2025, 3:24pm UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/13 "2025-08-21T15:24:05Z")

</div>

this one is fixed in today’s [1.1.2 update](https://forums.realmacsoftware.com/t/elements-1-1-2-23804/50028) 🙂

---

<div class="post-metadata">

**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\
**Post date:** [August 21, 2025, 6:08pm UTC](https://forums.realmacsoftware.com/t/cms-update-coming-next-week/49676/14 "2025-08-21T18:08:13Z")

</div>

And it is working great, thank you so much for getting this operational.
