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
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.
If you are running a licensed copy of Elements, please post all feedback in the Feedback Forum. You can use the Elements > Send Feedback… menu item to automatically pre-fill the build number into a new topic.
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!
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.
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.
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:
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.
