Elements 3.0 Beta Now Available

Happy cake day @Flash!

Thanks for the kind words, we are happy you are enjoying how the app is progressing and feel it’s maturing at a great pace! :heart_hands:

Just a heads up, I don’t develop the app, that’s @tpbradley @ben and @dan, so all the amazing stuff in the app is credited to their skills and hard work! :flexed_biceps:

My project and specialty is the Elements Hosting part of the new Elements Platform (along with Customer Support & Success), so if you have any feedback or questions about that feel free to tag me and let me know. :+1:

Oh gosh I feel bad. Sorry I forgot Tom @tpbradley !

Elements is in my Applications folder.

Then it might be stuck in translocation.

The Eclectic Light Company has a whole category about this, with tips on how to resolve it:

But try moving the app to your trash bin, emptying trash, then redownloading making sure to move it from Downloads to Application folder first before you try and open the app.

Hopefully the above helps.

Ah yes, it was named differently during development, so the correct name is as it appears in the UI - Text Wrap.

Yes, this works! However, in this first beta webp just works in preview, and not in edit mode, yet…

You can test this out for yourself in the beta :smiling_face:

@dan I ran into an interesting issue with the beta build. I have a number of cards that I use for items that can be downloaded from my site. When opening my project in the BETA the cards all end up looking like the image below.

If I then go into my card, where there is a footer container, and I go to the Flex & Grid settings for the container. Then if I go down to the Advanced/Basis setting (which is on Auto) and just reselect Auto, the problem goes away!

I’m curious what is going on here and if I have to be wary of this behavior showing up in other situations.

I forgot to mention that the container is set to the FLEX option in my case. Although I did just discover if I switched it to GRID then the issue also resolves itself.

Don’t ask me how I figured this out; pure luck, I suspect.

Wow :open_mouth: - you’re smart….

Yep I had made two custom themes - once I switched to an elements theme - it started working as expected….

No issues then for me…

Amazing :star_struck: - A perfect Beta….

Elements version TW4 need to test a bit more- elementsapp://downloadDocument/M1WGXGvBnnIp

Oh, interesting! Can you send us a sample project showing the issue? That way we can investigate further and see what’s going on and issue a fix :slight_smile:

Ah, this will be because the built-in themes have been upgraded to Tailwind 4, at a minimum you’ll need to add the following code to the info.json file in the theme:

"tailwindVersion": "v4",

like this…

Your custom theme will also be missing some of the new Tailwind colours, and some of the sizing classes will also be missing.

@dan Here is the link to the very simple project with just a single card that shows the problem.

NOTE: If you simply turn off the setting that makes the container behave like a flex, the problem will go away. I’m not sure I ever set it to originally be a flex, but then it has been some time since I looked at these cards.

BETA3 Card Issue

Roughly the same in one of my projects but for images. The width of the image was set to “auto” and after selecting “auto” again the size of the image is correct.

Yes, it does appear to have something to do with the AUTO setting.

I discovered it is the ReadTime component causing this appearance of a stray box with drop shadow. I put ReadTime into a Container and hid the container and the box goes away.

@Massimo

We’ve found the issue, and we’re seeing if we can fix it in the next update.

You can solve the issue now by re-selecting the “Basis” to “auto” in the Flexbox and Grid ->Advanced settings.

Can you share a project with this issue in? Thanks :blush:

Thanks @differentdan It does. If you follow Oakley’s direct advice, you end up with Elements back in the Applications folder with a new name (in my case Elements 7.40.53 AM.app). You then have to rename it back to just Elements.app if you don’t want the appendage.

Sure, as this is one of my templates I will send you the link to the project file via mail.

is this the correct one?
[REMOVED BY ADMIN]

Send it to forumsupprot@realmacsoftware.com

So, to get the new v4 features to apply to a custom theme, would you need to create a new theme from scratch? Is there any documentation for the json file that’s needed to make this work. Just by adding the tailwinds version to the file did not seem to work for me.