Elements CMS 2 Now Available

Issue solved is was [[ in some .md files

just to add to what Dan said, I’m afraid you might run in to a current limitation whereby you cannot remove or change the content folder on the free tier (this is a bug, it’s not deliberate).

For now, you’re going to have to reset your Online Editor installation by deleting the /rw/elements/com.elementsplatform.cms/editor/php/config.php file.

Deleting config.php removes the Online Editor setup/configuration, including the admin account and configured folders. It does not delete Markdown content or uploaded resources.

You can then re-run the install wizard and select the correct content folder.

Let me know if you need any more help :slight_smile:

That’s great to hear! Glad you’re up and running, let us know if you need any more help :slight_smile:

I’ll investigate this one and see what we can do :slight_smile:

That worked.

But I can see that I’m going to have to get the paid upgrade to manage things the way I like. I just need to determine whether the expense will be worthwhile in the long run. This is especially relevant considering that I have three different domains, each with its own blog. I might have to consolidate them all in one place.

@dan That does not appear to work if you are on the FREE plan, as that button states you cannot remove the last folder. I can see how it would work with the paid plan and the presence of multiple folders.

I followed Ben’s suggestion and simply deleted the config file and then started over, so now I can see all of my existing posts.

I can see how a paid version of the online editor would be handy, but it’s beyond my budget. I’ll have to stick with manually building my MD files and occasionally using the online editor when I’m away from my desk.

Just keep in mind that the edits you make online are not currently synced back down to Elements.

Certainly, it’s important to remember this.

@ben One other thing I have just discovered with the new CMS is that the LOAD MORE button on my blog page is no longer working. In fact, it is no longer even visible; for some reason, it does not show up on the page.

We’ve just pushed out an update Version 2.4.0 (24278), this should fix the issue for you :slight_smile:

Again, this should be fixed in the new build we’ve just pushed out, 2.4.0 (24278).

Let me know how you guys get on :+1:

Different project, different error message — even after the latest update.

I sent the project file directly to Ben.

Okay, thanks for the info, he’ll take a look in the morning :+1:

Hang in there, we’ll get all this sorted for you!

This is not going well for me but things happen. When I set up the admin page - it is blank. Then I disabled Cloudflare Rocket as it was a possible issue, Still a Blank Page. Purchased Studio but cannot find how to activate - is it through the admin page?

Failed to open https://excellentstreetimages.com/rw/elements/com.elementsplatform.cms/editor/v20260531/tailwind.css?rwcache=801005291
Failed to open https://excellentstreetimages.com/rw/elements/com.elementsplatform.cms/editor/v20260531/app/app.js?rwcache=801005291

Thanks everyone for the quick response and fixes. I know we’ve been pushing to get this released, so we appreciate all that you guys are doing. Just a reminder: lightbox on images still needs to be fixed.

@dan @ben

random image on load

this update does not fix my issues - elementsapp://downloadDocument/sG3d4BKlPOzn

first page has custom component to load image and link
second page just uses twig in background and image components

In the project below rand text loads but not random images
latest Elements version - (24278)

Prior to CMS 2 version - (24272)

Will there be a new instruction manual / Video?.. The older video had an Amin page, but this is no longer shown after the update. Very Confusing. All I need is the ability to assign images and text.

​Terrence

The collection pagination in my projects also no longer works under ECMS version 2.0.

The first update has already helped a bit …

However, I’ve noticed that images defined in my Markdown frontmatter like this:

media:
    header:
        src: "/0300-stores/0200-moebelmaerkte/ikea/header/800x450/ikea.webp"
        alt: "Verkaufsoffener Sonntag bei IKEA"
        copyright: ""
        type: "remote"  
    logos:
        logo_200x200:
            src: "/0300-stores/0200-moebelmaerkte/ikea/logo/200x200/ikea.webp"
        logo_300x300:
            src: "/0300-stores/0200-moebelmaerkte/ikea/logo/300x300/ikea.webp"
        logo_240x120:
            src: "/0300-stores/0200-moebelmaerkte/ikea/logo/240x120/ikea.webp"
        logo_300x250:
            src: "/0300-stores/0200-moebelmaerkte/ikea/logo/300x250/ikea.webp"
        alt: "IKEA Logo"
        type: "remote"

are not being output.

My assumption is that the Markdown parser does not recognize this structure properly.

Mine no longer works either.

Hi @Pegasus @upssjw,

the issue here is the CMS 2 not correctly prefixing the resources path for images. We’ll have a fix out for this today. This is not an issue with your frontmatter, it’s an issue with the new CMS.

Fix incoming, stay tuned :smiley: