Elements 1.1.2 (23804)

Elements Builds
1

Hello again,

For an in-depth look at some of the new features in Elements 1.1.2, check out today’s Dev Diary!

Please note: This new build finally introduces the “Made with Elements” badge to the base plan. If you’d like to remove this badge from your website you’ll need to upgrade to the Plus plan, this can be done from the Subscriptions tab in the Preferences (aka Settings) window.

What’s New in Elements 1.1.2?

  • Huge improvements to resource import, project saving, icon generation and memory use
  • Added support for batch Import of Remote Resources
  • Option for “New Folder from Selection” in resources is back
  • Page list now prevents dragging to a child of a code page
  • Fixed dev pack link in app preferences
  • New Elements Badge Component
  • Added “Made with Elements” Badge to Base plan websites
  • Added an option in the Menu Component to specify at what breakpoint the mobile menu appears
  • Fixed an issue with the Image Component not resizing images in Preview/Publish
  • Added support for alt tag in CMS on the Image Component
  • Load More CMS Component now works on sub pages
  • Collection Item links ({{item.url}}) in the CMS now work when the site is published to a sub folder
  • Missing CMS Frontmatter props no longer causes a fatal error
  • Added support for Custom source (url, php, etc…) in Image Component
  • Time is now respected for date filtering in the CMS, you can now use “2025-08-21 17:00”. Time is in UTC, customising the timezone is not currently supported.

Purchase a License

You can visit the elementsapp.io website 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.

Give Feedback

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.

2 Likes
2

Just tested this and yes it is working but it assumes the timezone is GMT | UTC. I realise timezone (as noted) isn’t supported yet but maybe when it is it should also have an option to see whether to honour Daylight Saving Time?

EDIT: Also maybe have an option as to whether to take account of the time (if present) or not when deciding whether to publish i.e. this could be a toggle in the Filters section.

3

Yes, we need to spend some time and figure out the best way to support timezones in the CMS code. It’s already on the list to investigate, but for now you’ll have to rely/fallback on UTC time :slight_smile:

1 Like
4

@ben Thanks for fixing the Load More button issue. It works great now.

Is there a way to support Previous and Next buttons on the individual post page, so that a user can step through the posts? I added a Posts button to my page so they can get to the main page, but it would be nice to be able to cycle through the posts.

5

Not at the moment, however, we will be adding more CMS components over time.

6

I look forward to those as it would be nice to allow the user to flip through the posts.

7

this is very welcome, next step a full vertical menu and we ave all tools to make something more in design :slight_smile:

1 Like