RapidWeaver Elements 2.4.2 Now Available

[dan]

Hey Weavers,

We’re back with another build of Elements, with more polish on the Online Editor and broader server compatibility. If you haven’t watched the launch videos yet, you really need to. The integration and workflow possibilities with AI is mind-blowing

Elements CMS 2 Available Now!

Connect Claude to Elements CMS for Blogging Superpowers

What’s New in Elements 2.4.2?

• Markdown parser no longer throws fatal error when closing quotation is missing
• Adds fileinfo to server requirements on setup
• Add MIME detection helpers so resource listing does not fatal when PHP Fileinfo/finfo is unavailable
• Fixed related item URLs
• Fixed an issue with Pretty URLs setting not always being respected

Crossgrade to Elements

Not using Elements yet? Get 25% off when you crossgrade from Blocs, Sitely, or any other Mac-based website builder. The offer also applies to RapidWeaver Classic and Stacks users. Feel free to share the link below, it automatically applies the discount at checkout.

Get 25% off Elements for macOS today

System Requirements

In order to run Elements you will need to meet the minimum requirements:

• Requires macOS 13 Ventura or newer.
• Apple Silicon or Intel based Mac.

The trial mode in Elements has the following limitations:

• No publishing: You can’t upload or publish sites in trial mode.
• No export: Exporting project files is disabled.
• Maximum of 3 pages: You can only add up to three pages per project.

Download Elements for macOS

How to rollback to a previous build

Should you run into an issues when using a new build of Elements you can always rollback to a previous version via the Release Notes page while you wait for a fix.

The Future of Web Design

Thanks for being part of Elements and for helping us shape the future of web design on the Mac. Your feedback during the beta has been hugely valuable and played a big role in where Elements goes from here.

We’re excited to keep building, refining, and shipping, and we really can’t wait to show you what’s coming next.

Thanks
Team Elements

[Pegasus]

I’ve discovered another issue on one of my websites.

For my blog post collection, I’m using the Pagination component to navigate through the blog posts.

In addition, I’m also using another CMS Collection Item on the same page, which serves as a kind of navigation.

When I load the page normally, the content of the second collection is displayed correctly. However, as soon as I navigate back and forth using the pagination, the content of the navigation component disappears.

@ben Do you have any idea what might be causing this?

[handshaper (Robin Mair)]

Fantastic.

All of my CMS 2 issues are now resolved.

[ben]

both collections will be picking up the ?page={number} query parameter in the URL, and therefor both will be paginated.

This sounds like expected behaviour to me as there is currently no way to turn off pagination on a collection.