CSS failure with CMS in Elements 2.1.1

I’ve had issues with the newest release of Elements - v2.1.1. The CMS was working perfectly until I made some changes to colours and re-published. From that point on the posts failed to render properly and the error log showed that it was trying to find the CSS in the wrong directory with a peculiar path:

[08-Mar-2026 00:03:45 Europe/London] CMS Item not found: ../cms/posts post.css

The directory cms/posts is where the Markdown text lives. The css for the Post page itself is found at post/post.css.

Is this an Elements bug or is there something that has gone wrong within my project? When I preview the Post page within Elements it renders correctly. It just fails to link the CSS when published.

The Elements Cloud version is at: elementsapp://downloadDocument/eulM0mt796i6

An example of the result is at Post

@dan Any thoughts on this one Dan? Am I doing something wrong?

Hi @curlypaws

I’ve jut had a look at your site, and I think the issue could be that you’re setting the individual post page’s filename to be post.php instead of index.php — is there any specific reason why you’ve done that?

Could you try setting the Post page’s filename to index.php, republishing all files, and then testing if the page works as expected?

1 Like

It looks like a user who has switched from TCMS to the Elements CMS.

Setting the blog post entries to filename to be post.php is a common approach to achieve a cleaner and more meaningful URL structure.

For example:

/blog/?item=my-blog-post

Whereas in Elements it usually looks like this:

/blog/post/?item=my-blog-post

But I might also simply be mistaken.

1 Like

Thanks very much @ben and @Pegasus , changing the page name back to index.php did the trick.

I had started trying to change the names to more meaningful ones but didn’t realise that would cause issues for the CMS.