This update brings a raft of improvements, and perhaps my favourite “new feature” is the new Liquid Glass app icon designed by Parakeet, I think it looks great, and yes we have a new icon coming for RapidWeaver Classic too
Anyway, I hope you’ll agree that Elements is feeling better with every release and is fast becoming the solid, dependable website builder we’ve always wanted it to be!
Let’s jump in and check out what’s new…
What’s New?
Added new Tahoe Liquid Glass app icon designed by Parakeet.
Prevent publishing when your website address uses an unsupported URL scheme (non-http/https) and fix related crashes.
Fixed a crash that could occur while exporting multiple pages at once.
Fixed a crash when opening a damaged project package.
Updated the MCP installer and element packs for improved compatibility and stability.
CMS: Updated the installer for a smoother setup experience.
CMS: Replace the “Who can edit” checkbox list with a searchable picker for faster editor selection.
CMS: Allow setting editors per item in shared content folders to fine-tune access.
CMS: Support optional allowlists on content and resource folders to restrict who can edit them.
CMS: Add an opt-in recursive mode that automatically includes collection items in subfolders.
CMS: Record who made each CMS edit and include it in webhooks and version history.
CMS: Show custom branding on the editor login page even on a cold load.
Get the Update
Elements should prompt you to update when it is running. You can also use Elements → Check for Updates….
Are there or can there be features in the future that allow Claude to
Create or move resource folders?
I am currently converting a lot of jpgs to webp files and a simple command to Claude to move, create or delete resources would speed up things.
Also come across a situation where Claude didn’t know which file a video component was playing. I had to let it have access to the project file directly so it knew.
Sorry about that. Could you check the website address in your project’s General site settings and make sure it’s a full address starting with http:// or https://? 3.1.4 added a check that blocks publishing when the address isn’t http or https, and that may be what’s stopping Preview.
Scrap that! We’ve confirmed that Publish Preview doesn’t work in 3.1.4 on macOS 26 and earlier. The PHP bundled with that build was built for macOS 27, so the preview server silently fails to start. We’ve pulled the 3.1.4 build, and a fixed build will be out as soon as possible. It shouldn’t be long.
I have problems installing the update. First I got a message that 3.1.4 is available. I then pressed update but it failed with an error message - I didn’t pay attention but something with an archive what cannot be found or extracted.
