ben
April 30, 2026, 4:31pm
42
Not released yet, we’re working as fast as we possibly can to get it in your hands. I don’t want to give a date, but we’re hoping it’ll be in the very near future.
We haven’t announced pricing just yet, we’ll be doing that as we get closer to launch.
Not yet, we’re still working on the site and all the final details, however, you can get more information on all the feature (both free and paid) on the Online Editor page .
We hope to have an updated project ready before launch, alongside more detailed documentation and additional video tutorials.
dan
April 30, 2026, 5:15pm
43
The Microblog Project is now available in the app, check the New Project window
ben
April 30, 2026, 5:37pm
44
I’ve just posted some more details about what’s new in CMS v2 . We’ll be posting more information about features and pricing on the blog as we approach launch date, stay tuned
Thanks for your answers, Ben.
Pegasus
May 8, 2026, 10:02am
46
@ben
I’d like to come back to an issue with the related item feature, which does not work correctly in certain situations.
I noticed that when the filename of the Markdown file does not match the name of the webpage or folder, the related item no longer works and returns the error “No item found.”
However, “No item found” is only displayed after the website is published. In the local browser preview, the correct related item is still displayed normally.
Example that works:
my-markdown-file-one.md
my-markdown-file-two.md
/my-markdown-file-one/
/my-markdown-file-two/
This does not work
my-markdown-file-one.md
my-markdown-file-two.md
/markdown-file-one/
/markdown-file-two/
So this means the Markdown files currently always need to have exactly the same name as the webpage or folder.
Since the related items are displayed correctly in the local preview, I assume this should also work after publishing and that this is likely a bug.
If this hasn’t already been fixed, could it be added to the CMS 2.0 to-do list?
Here’s another older forum post regarding this issue:
@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:
2025-month-day_title.md
However, when Markdown files are named simply:
one.md
two.md
three.md
four.md
five.md
…the related items feature does not work,…
Pegasus
May 8, 2026, 2:35pm
47
There is another issue I noticed in CMS version 1.0 .
I quite often use title and aria-label for external and internal links.
For example, if I use the following Twig syntax as the value for a link:
{{ "this sunday"|date("d.m.Y") }}
it does not render correctly when used in both title and aria-label , and I get the following error message:
If I then remove the Twig syntax from either aria-label or title , everything is rendered correctly and the output works normally without any error.
Would it also be possible to fix this in CMS 2.0 , so that multiple Twig syntaxes can be used in the custom attributes when creating links?
ben
May 8, 2026, 3:49pm
48
Features and fixes for the v2 release are now set, so unfortunately this not something that will make it in to the first v2 release.
We can take a look at this one soon after release though
ben
May 8, 2026, 3:51pm
49
I’m wondering if the issue here is actually that you’re using double-quotes in the title and aria-label values. Maybe try switching those to single quotes and see if it works.
Pegasus
May 8, 2026, 7:20pm
50
It does indeed seem to be those sneaky little double quotes causing the problem…
Thanks for the hint. It’s just a bit annoying for me now, because I’ll have to change my whole site over to single quotes.
dan
May 13, 2026, 2:46pm
51
Pegasus:
is this fixed in CMS2?
@ben The rel=“canonical” tag does not work in Elements CMS. While checking and reviewing the source code, I just discovered that for blog posts in Elements CMS, the SLUG is not being correctly replaced in the rel=“canonical” tag. See the screenshot. [Bildschirmfoto 2025-09-15 um 22.48.11] It would be great if this could be fixed so that the blog posts can be indexed by Google. Also, when I activate the Open Graph meta tags under the CMS item, they are also not being replaced or outputted. …
This has been fixed {{item.canonicalUrl}} tag you’ll be able to use on post pages, like this…
Pegasus
May 13, 2026, 2:58pm
52
That’s exactly the solution I had in mind. Now all that’s missing is the CMS 2.0.
As we can see, it works too
Pegasus
May 14, 2026, 10:04pm
53
@ben CMS version 2.0 .
Is there a simple search function in the online editor? In other words, is there a way to search for blog articles or blog posts?
That was always a bit difficult in ALLOY — especially when you had several hundred posts and wanted to edit a specific one.
If this isn’t already included, maybe it could be considered as a future update for the Pro version. It would definitely be a very useful feature.
Another perhaps stupid question:
this goes once on the ‘post’ page…
Do I need to put this also in each mark down page?
Thanx
Trying to understand…
ben
May 15, 2026, 7:32am
57
No, the canonicalUrl is automatically generated based on your site URL and the item slug.
You don’t need to do anything, the CMS will do all the work for you.
Hope that makes sense
and there’s a new 
