# CSS failure with CMS in Elements 2.1.1

**URL:** <https://forums.realmacsoftware.com/t/css-failure-with-cms-in-elements-2-1-1/54955>\
**Category:** Elements CMS\
**Created:** [March 8, 2026, 10:15am UTC](https://forums.realmacsoftware.com/t/css-failure-with-cms-in-elements-2-1-1/54955 "2026-03-08T10:15:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![curlypaws](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/curlypaws/32/3964_2.png) [@curlypaws](https://forums.realmacsoftware.com/u/curlypaws)\
**Post date:** [March 8, 2026, 10:15am UTC](https://forums.realmacsoftware.com/t/css-failure-with-cms-in-elements-2-1-1/54955/1 "2026-03-08T10:15:02Z")

</div>

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](http://www.curlypaws.com/post/post.php/?item=kef-ls50)

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

---

<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:** [March 9, 2026, 11:29am UTC](https://forums.realmacsoftware.com/t/css-failure-with-cms-in-elements-2-1-1/54955/2 "2026-03-09T11:29:01Z")

</div>

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?

 ![CleanShot 2026-03-09 at 12.26.11@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/3/4/34aa057b3a157fbb1ba89f815a562b50fe02d8a0.png)

---

<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:** [March 9, 2026, 11:59am UTC](https://forums.realmacsoftware.com/t/css-failure-with-cms-in-elements-2-1-1/54955/3 "2026-03-09T11:59:54Z")

</div>

> [@ben](#):
>
> filename to be `post.php`

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.

---

<div class="post-metadata">

**Author:** ![curlypaws](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/curlypaws/32/3964_2.png) [@curlypaws](https://forums.realmacsoftware.com/u/curlypaws)\
**Post date:** [March 9, 2026, 12:34pm UTC](https://forums.realmacsoftware.com/t/css-failure-with-cms-in-elements-2-1-1/54955/4 "2026-03-09T12:34:54Z")

</div>

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.