RapidWeaver Classic 10 Beta 1 Now Available

Hey Weavers,

As promised, we’re continuing to support and update RapidWeaver Classic for those of you who haven’t yet made the move to Elements.

We’ve been busy getting Classic ready for the latest versions of macOS. This has included a substantial UI refresh, helping it feel more at home with Apple’s refined Liquid Glass design in Golden Gate. We’ve also added some new features, fixed plenty of bugs, and made a number of performance improvements.

If you’re already running Golden Gate, you’ll probably have noticed that the current RapidWeaver icon is stuck in “Squircle Jail”. The good news is that we’re working with a third-party design agency (named after a bird) to create a brand-new icon for Classic. It will make its debut in the public release of RapidWeaver Classic 10 later this year.

Let’s dive into what’s new in the first beta of RapidWeaver Classic 10 below…

What’s new in Classic 10.0 Beta 1

RapidWeaver Classic 10.0 requires macOS 12 or later.

Interface

  • Settings, preferences, and the built-in plugins have been updated for current versions of macOS, including macOS 27.

Publishing

The publishing engine has been updated, bringing better connection diagnostics, improved stability, and more reliable handling of FTP and Amazon S3 destinations.

  • Limit upload speeds. Publishing preferences now include a “Limit uploads to” option, which caps the combined upload speed of all active connections in KB/s. It is off by default and does not apply when publishing to a local folder.
  • Better connection diagnostics. Connection tests now show DNS lookup and TCP connection times, making firewall, routing, and latency problems easier to identify.
  • FTPES naming. Explicit FTPS is now labelled FTPES to match the terminology used by most hosting providers. This is a naming change only; the connection method is unchanged.
  • Amazon S3 regions. Publishing now uses the selected bucket’s own region.
  • Improved FTP stability. Fixed a crash that could occur when several FTP connections were active at the same time.

Editing and Preview

  • Preview export errors now appear on the affected document instead of in an app-wide alert that could cause a crash.
  • Dragging items in the project outline no longer causes a crash.
  • Fixed a crash when clicking a site resource on macOS 27.
  • Fixed a crash caused by folders inside Site Resources when activating a site.
  • Choosing Cancel or pressing Escape when removing blog entries no longer deletes them.

Contact Form

  • Authenticated SMTP. Contact Forms can now send through an authenticated SMTP server, including Elements Hosting. Existing sites continue using PHP mail() unless SMTP is enabled.
  • Built-in spam protection. A hidden honeypot field rejects automated submissions before an email is sent.
  • Improved PHP 8 compatibility. Messages sent through PHP mail() remain intact and no longer expose the raw MIME boundary.
  • Safer SMTP port handling. Clearing the port field no longer causes a crash. When left empty, the port defaults to 587.
  • Password handling. SMTP passwords remain saved with the original document but are omitted when a page is copied or duplicated.

Photo Album

  • Thumbnails now remain visible when an image cannot be read.
  • Clearing a numeric setting no longer causes a crash.

Pricing and Beta Availability

This is a free update for everyone with an active Classic licence. To get beta access, open the Preferences window, go to the Updates tab and enable the “Check for Beta updates” option.

Ongoing Support for Classic

We know many of you have built your workflow around RapidWeaver Classic, and we want to reassure you: Classic isn’t going anywhere. We’re continuing to maintain and update it with important improvements, fixes, and optimisations to keep things running smoothly!

Give us your Feedback

As this is a beta please let us know if you run into any issues, or if there are any other long-standing issues you’d like to see fixed and we’ll do out best to get them into the next beta.

Happy Weaving!

Is it strange to go back to classic for development?

It is so different from elements…

Very nice to continue classic….

Classic is a much simpler app, so in some ways it’s easier to update than Elements. But anyway, it’s nice to be back providing updates to everyone still using and relying on it :blush:

Viva-la-classic-weaver!