Elements CMS 2 Coming Soon!

[Pegasus]

@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:

BUGS in Elements CMS Build 1.5.5

@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,…