# RapidWeaver Classic 10 Beta 5 Now Available

**URL:** <https://forums.realmacsoftware.com/t/rapidweaver-classic-10-beta-5-now-available/58115>\
**Category:** Announcements\
**Created:** [November 11, 2026, 8:30pm UTC](https://forums.realmacsoftware.com/t/rapidweaver-classic-10-beta-5-now-available/58115 "2026-11-11T20:30:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [November 11, 2026, 8:30pm UTC](https://forums.realmacsoftware.com/t/rapidweaver-classic-10-beta-5-now-available/58115/1 "2026-11-11T20:30:07Z")

</div>

Hey Weavers,

We’re back with another build of RapidWeaver Classic, this build continues our work on polishing and improving Classic. Not too much of note, but there is an updated licensing system, so be sure to look out for any anomalies!

Please let us know what you think of classic, and if there’s any features you’d like to see implemented, we’re all ears​👂

### What’s New in Classic 10 Beta 5

- Added a site setting to opt published pages out of Safari Adaptive Dark Mode.
- Added updated DevAnt licensing system.
- Various other fixes and improvements.

### RapidWeaver Classic 10 Updates so far…

- Classic now requires macOS 12 or later.
- Updated settings, preferences, and built-in plugins for current macOS versions, including macOS 27.
- New Tahoe Liquid Glass app icon designed by Parakeet.
- Added native PHP build support for macOS 12 and later
- Fixed attachment display and interactions on macOS 27 for improved compatibility.
- Updated to PHP 8.4.27 and PHP 8.5.12.
- PHP build versions are now derived from the bundled filenames.
- Added an optional upload speed limit shared across all active remote publishing connections.
- Publishing connection tests now show DNS lookup and TCP connection times.
- Explicit FTPS is now labelled FTPES.
- Amazon S3 publishing now automatically uses the selected bucket’s region.
- Fixed a crash when multiple FTP connections were active.
- Preview export errors now appear on the affected document, avoiding a potential crash.
- Fixed a crash when dragging items in the project outline.
- Fixed a crash when clicking a site resource on macOS 27.
- Fixed a crash caused by folders inside Site Resources when activating a site.
- Clicking Cancel or pressing Escape when removing blog entries no longer deletes them.
- Added authenticated SMTP support to Contact Forms, including Elements Hosting. PHP `mail()` remains the default.
- Added built-in honeypot spam protection to Contact Forms.
- Fixed MIME formatting in Contact Form emails sent using PHP 8 `mail()`.
- Clearing the SMTP port field no longer causes a crash. Empty ports default to 587.
- SMTP passwords remain saved in the original document but are omitted when a page is copied or duplicated.
- Photo Album thumbnails remain visible when an image cannot be read.
- Clearing numeric settings in Photo Album no longer causes a crash.
- Blog RSS feeds now satisfy W3C validation checks
- Plugin inspector tabs now appear correctly on macOS 13
- Fixed a photo album crash caused by clearing numeric fields
- Continued work on improving the codebase and fixes minor issues
- Fixed Classic Blog RSS to meet W3C validation and prevent podcast publishing crashes.

## 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.

 ![CleanShot 2026-10-01 at 7.44.24 PM@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/f/2/f21135196c8db3bba650a64e59226c73b4de5e62.png)

## **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.

If you’re license has expired, you can [purchase another year of updates over on the Realmac web store](https://www.realmacsoftware.com/rapidweaver-classic/purchase/).

## **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!

---

<div class="post-metadata">

**Author:** ![APSS](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/apss/32/30562_2.png) [@APSS](https://forums.realmacsoftware.com/u/APSS)\
**Post date:** [November 11, 2026, 9:22pm UTC](https://forums.realmacsoftware.com/t/rapidweaver-classic-10-beta-5-now-available/58115/2 "2026-11-11T21:22:26Z")

</div>

@Dan, I cannot begin to express my gratitude enough that you have put new life into Classic. I didn’t see any reason such an amazing software should have died a slow, agonizing death. With all the hype behind Elements, and I am sure it’s a good platform, I couldn’t see why, the same way **WordPress weathered many storms** , RapidWeaver couldn’t maintain its foundations.

When WordPress introduced its new block editor (Gutenberg), it shook the entire developer ecosystem. There was immense backlash from veterans who preferred the classic way of doing things. But instead of leaving those users in the dark or abandoning their old architecture, WordPress kept providing a dedicated “Classic Editor” plugin. They recognized that millions of existing websites rely on that stability to stay alive. Even during their most recent corporate and legal battles, the core philosophy remained clear: you don’t grow a new platform by burning down the house your loyal community already built.

I have almost a dozen websites built on Classic, including a massive project at thelightroom.press with extensive subdomains and HTML book publications. Moving all of that over to a completely different “concept” like Elements wasn’t just inconvenient; it was a business-killing hurdle.

You are choosing to respect **not only developers who build websites for a living, but also book and blog publishers who only need a software that works and provides stable, enduring tools.** Thank you for listening to us and protecting our investments.
