# Elements 1.2.0 (23816) **URL:** \ **Category:** Announcements\ **Created:** [August 27, 2025, 5:39pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281 "2025-08-27T17:39:21Z")\ **Posts on this page:** 20\ **Page:** 1
**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 27, 2025, 5:39pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/1 "2025-08-27T17:39:21Z")
Hello again, This build introduces the “Import Classic Project” feature, we’re shipping this feature early, and due to that, have labeled it as beta. **We really wan’t your feedback** on this feature. Take it for a spin, and let us know how you get on. Does it do enough to get you going in Elements? or is something missing? **Let us know!** Oh, and we’ve also fixed a publishing/export bug, and managed to squeeze in a few new features… with plenty more on the way 😉 ## What’s New in Elements 1.2.0? - Added Classic project import (Beta) `File > [Beta] Import Classic project…` - Fixed “hang on export” publishing issue - Added right-click sort options to resource folders - Fetch Priority option added to Images, and Background Images - New Hero Photo in Core Templates - New Photography Backgrounds in Resources ## Purchase a License You can visit the [elementsapp.io website](https://www.elementsapp.io/purchase/?utm_source=realmacsoftware-forum) to purchase a license. ## Get the Update Elements should prompt you while it’s running to let you know there’s an update. If it doesn’t, you can select the “Check for Updates…” menu option from the “Elements” app menu. Alternatively, you can always [download the latest build of Elements here](http://realmacsoftware.com/download/elements/). ## Give Feedback If you are running a licensed copy of Elements, please post all feedback in the [Feedback Forum](https://forums.realmacsoftware.com/c/rapidweaver-elements/beta-feedback/57). You can use the Elements \> Send Feedback… menu item to automatically pre-fill the build number into a new topic. ---
**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\ **Post date:** [August 27, 2025, 6:16pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/2 "2025-08-27T18:16:23Z")
No CMS Beta fix today? ---
**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 27, 2025, 6:18pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/3 "2025-08-27T18:18:47Z")
Publishing okey now, thanks. ---
**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 27, 2025, 6:20pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/4 "2025-08-27T18:20:19Z")
Publishing fix more important … ---
**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 27, 2025, 7:08pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/5 "2025-08-27T19:08:18Z")
> [@mrTablet](#): > > No CMS Beta fix today? What was the fix you needed in the CMS? ---
**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 27, 2025, 7:17pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/6 "2025-08-27T19:17:05Z")
> [@dan](#): > > What was the fix you needed in the CMS? is this fixed in the next cms-update? > [@Dev Diary 93 - CMS Early Access Beta fire](https://forums.realmacsoftware.com/t/dev-diary-93-cms-early-access-beta/49493/31): > > @ben first bug. I always use the option in Elements to assign the URL slugs myself. But when I enter /blog/ in the Folder field, I always get this error message. However, if I remove the path, everything works. ---
**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 27, 2025, 7:30pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/7 "2025-08-27T19:30:42Z")
You don’t need to add the extra slashes: > Try not to enter the “/blog/” for the folder name, leave out the “/../”, just “blog”. I have never had to do that with Elements, and it works fine. Was there any other issues you needed fixing? ---
**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 27, 2025, 7:45pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/8 "2025-08-27T19:45:41Z")
@dan sure!? ![Bildschirmfoto 2025-08-27 um 21.42.07](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/a/2/a20088a30db6b037f895e82d0589b88bfd351237.jpeg) ---
**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\ **Post date:** [August 27, 2025, 7:50pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/9 "2025-08-27T19:50:14Z")
> [@dan](#): > > What was the fix you needed in the CMS? Capital letters are automatically converted to lowercase on the server. ---
**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 27, 2025, 8:00pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/10 "2025-08-27T20:00:51Z")
I was just about to ask you to release an update for the “cms-beta badge” because I often have a lot of CMS items in my projects and had to disable them individually each time… but now I see you’ve already removed it. That’s fantastic—problem solved! ---
**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 27, 2025, 8:01pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/11 "2025-08-27T20:01:25Z")
Why are you trying to write in full folder paths? Don’t do this. Elements handles this for you, see the examples below: ![CleanShot 2025-08-27 at 8 .59.41@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/3/c/3c15a8240775c0194e0ff5cf9fd9fa74fdae4c76.jpeg) And I you wanted a different folder name to the page, you just do this: ![CleanShot 2025-08-27 at 9 .00.19@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/1/3/132f449c7178852a4208c0f7cb6adfaf8c0a3a7a.jpeg) ---
**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 27, 2025, 8:02pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/12 "2025-08-27T20:02:31Z")
> [@mrTablet](#): > > Capital letters are automatically converted to lowercase on the server. I believe this bug was fixed, we now publish the CMS backend with lowercase files. If this is still an issue please let us know exactly what you’re seeing and we’ll get it fixed. ---
**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\ **Post date:** [August 27, 2025, 8:04pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/13 "2025-08-27T20:04:49Z")
> [@dan](#): > > I believe this bug was fixed, we now publish the CMS backend with lowercase files. If this is still an issue please let us know exactly what you’re seeing and we’ll get it fixed. Still converted to lowercase on my server. ---
**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 27, 2025, 8:05pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/14 "2025-08-27T20:05:51Z")
That doesn’t make sense… what files are still converted to lowercase on your server? ---
**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\ **Post date:** [August 27, 2025, 8:08pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/15 "2025-08-27T20:08:56Z")
Images name does. ---
**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 27, 2025, 8:12pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/16 "2025-08-27T20:12:03Z")
When Publishing, Elements will lowercase all resource filenames and ensure they are websafe by swapping out foreign characters and spaces with an underscore. For example: - `my~file.png` would become `my_file.png`. - `my file has spaces.png` would become `my_file_has_spaces.png`. - `myFile.png` would become `myfile.png`. If you are referencing image paths in your Markdown files you should ensure they are all using lowercase names, otherwise the CMS may not render correctly depending on the server. * * * Many web servers (Linux/Unix based) treat File.jpg and file.jpg as two different files. However, on Windows or macOS (i.e. Elements), the filesystem often isn’t case-sensitive, so it _looks_ fine locally, but when uploaded, it can cause broken links and 404 errors. By using lowercase files, you’ll ensure they will ALWAYS work on different environments (Windows, Linux, macOS), this could be important if you ever move hosting companies. ---
**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\ **Post date:** [August 27, 2025, 8:14pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/17 "2025-08-27T20:14:44Z")
Maybe it has something to do with the fact that they are already changed to lowercase? ---
**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 27, 2025, 8:19pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/18 "2025-08-27T20:19:34Z")
![Bildschirmfoto 2025-08-27 um 22.04.39](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/f/0/f0c59fa62a32c065f2a5c0fb9c5c6f479c7aa0e9.png) As you can see, Elements doesn’t handle our “German” special characters correctly. Additionally, there are times when I want to keep the page/menu title short, for example “Mai”, but I’d like the URL to have a different name—for example, /termine/events-mai/. So far, this has worked just fine in Elements. However, when I add a CMS Item or a CMS Collection, I get the same error described in this post: > [@](#): > > @ben first bug. I always use the option in Elements to assign the URL slugs myself. But when I enter /blog/ in the Folder field, I always get this error message. [[Bildschirmfoto 2025-08-06 um 17.08.57]](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/b/4/b418d6ea5f8eea9487d9f63cc676d144c201bc46.png) However, if I remove the path, everything works. [[Bildschirmfoto 2025-08-06 um 17.06.39]](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/8/e/8e014ed0350988002c41287666d6cfc9993a7cdf.png) For me, this means the CMS has a problem with this setup, and it would be great if this could be fixed—since it works without the CMS. ---
**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 27, 2025, 8:21pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/19 "2025-08-27T20:21:58Z")
> [@mrTablet](#): > > Maybe it has something to do with the fact that they are already changed to lowercase? Are you referencing images using camel case in your Markdown files? ---
**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 27, 2025, 8:25pm UTC](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281/20 "2025-08-27T20:25:30Z")
@Pegasus, I’ve created a ticket for this and we’ll look into it further and see if we can work out a solution to this complex issue. [Next page](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281.md?page=2)