RapidWeaver Elements 2.4.1 Now Available

Announcements
, ,
1

Hey weavers,

Hot on the heels of yesterday’s huge CMS Online Editor release, we have an update that fixes a bunch of bugs that slipped through the net. We’ve also updated the built-in Microblog project with Search and an Admin area.

What’s New in Elements 2.4.1?

  • Added search and an online editor to the Microblog project
  • Improved the online editor’s asset loading to avoid caching issues
  • Fixed the Load More button on unlicensed installs
  • Improved frontmatter handling to better support legacy content and encodings
    • Preserved UTF‑8 characters during duplicate frontmatter cleanup
    • Normalized legacy frontmatter text to prevent garbled characters
    • Allowed duplicate frontmatter properties for compatibility with older content
    • Fixed incorrectly prefixed resource paths in nested frontmatter

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.

:backhand_index_pointing_right: 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.

:backhand_index_pointing_right: 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

2

Thank you :blush:

3

You’re welcome as always :saluting_face:

4

Pagination is working also. Thanks for the quick updates.

5

Yesssssss!!

7820158128199432

6

images work now excellent

7

Yes! That is awesome!
8093928781287394

8

@dan LOAD MORE is sort of working now.

What I have found is that when you load more posts, clicking on one of the now-visible posts will give you a “page not found” error. But if you expand the number of visible items on the blog page, one of the items that could not be found works fine.

I still have a problem with my dimension table where an entire collection of items is not being displayed, but all of the other collections work just fine.

9

I’ll get @ben to take a look at this tomorrow morning for you!

In the meantime can you send your project over to forumsupport@elementsplatform.com

10

The projects I sent to Ben by email are now working for me again as well, including the pagination.

However, I’ve just sent Ben another project directly by email which is unfortunately still showing a Fatal Error message. This error disappears, though, as soon as I disable the Related Item.

So once again, thank you for the quick and solid support, and for the update.

11

No problem, we’ll dig into all these smaller issues tomorrow and hopefully get it all resolved. Stay tuned!

12

I emailed in the project; thanks for taking a look.

13

I tracked this down to malformed YAML front matter in a couple of your Markdown files. One of the description fields starts with a normal double quote but ends with a smart quote, so the front matter parser cannot read it.

Related Items made the issue visible because it scans the other items in the same collection to find matches, so a single malformed item can trigger the error even when viewing a different page.

We’ll tighten up the parser so it can recover from this specific quote mismatch, but correcting the front matter quotes in those Markdown files will also resolve the issue.

Affected content files I found:

  • kochen-ist-leidenschaft.md (line 36)
  • kochen-leicht-gemacht.md (line 39)

Both have description.short values that open with a normal quote " but close with a smart quote “, which makes the YAML front matter invalid.

14

I really can’t say thank you to @ben often enough.

Little details like normal quotes " and smart quotes “ are easy to overlook when you’ve been sitting in front of the screen all day — or, like me, if you simply had no idea there was even a difference ^^.

You honestly can’t really see the difference in the inline Markdown editor in Elements. Hopefully, that kind of thing won’t happen as often in the future once the online editor is in place.

Anyway, I’ve adjusted everything now, and it’s working again.

15

Hello,
my RW 8 open anymore on my new MacBook Air 26.5

???

Guenther

16

I’ve replicated this bug, working on a fix for it now!

17

This is due to some malformed frontmatter. Looking through the markdown files for the Q5 Series: I found an issue in Q5-375C.md: Indentation is broken in the dimensions block:

dimensions:
        title: "Q5-375C Center"
height: "3.75\" / 95mm"
    base: "2.875\" / 73mm"
    area: "7.94in<sup>2</sup> / 51cm<sup>2</sup>"

Two problems here:

  • title: is over-indented (8 spaces instead of 4)

  • height: has no indentation at all, so it’s parsed as a top-level key rather than part of dimensions

It should match the pattern in the others:

dimensions:
    title: "Q5-375C Center"
    height: "3.75\" / 95mm"
    base: "2.875\" / 73mm"
    area: "7.94in<sup>2</sup> / 51cm<sup>2</sup>"

Once you fix that the Q5 section will be populated. Let me know if that works for you :slight_smile:

18

Is it possible to create relationships between collections with the CMS Studio license? Here’s what I mean…
Suppose we have two collections:

  • a “product” collection (with the title, image, and description properties)
  • a “details” collection (with the title, image, and description properties)

What I’d like is to use the fields in the “product” collection to select items from the “details” collection (with the title or id property selected) so that they are displayed on the post page of the “product” collection. And obviously, the selected items from the “details” collection must also include the other properties, meaning that in an item from the “product” collection I can also display the contents of one or more items from the “details” collection.

And then it would be nice to have at least a CMS component that allows data/content to be displayed conditionally, that is, based on the value of other properties.

Is this feasible currently? If not, will it be possible in the near future?

19

Wow, that indeed did fix it. It’s intriguing that it used to work before, as I never noticed that this one was malformed.

Thanks so much for tracking this down.

Going forward, I will be more stringent checking the front matter.

20

@ben I have a question related to this, as I have been doing a lot of testing trying to get the problem resolved on multiple sites.

From what I can tell, you have to use FOUR actual spaces, instead of a TAB that is set to FOUR spaces, correct?

Which is what I tried in BBEdit, and that immediately broke the collection.

UPDATE:

I think I finally figured out that I need to set BBEdit to AutoExpand Tabs, and then it will convert them to spaces. Seems to work when I test it.