We’re back with another beta update for RapidWeaver Classic, this is just a small one as we continue to improve the underlying codebase and fix any remaining issues under macOS Golden Gate.
Lots more good stuff to come, please let us know what you’d like to see in Classic!
What’s New in Beta 2?
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
Beta 1 Updates (incase you missed it)
Classic now requires macOS 12 or later.
Updated settings, preferences, and built-in plugins for current macOS versions, including macOS 27.
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.
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.
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.
I am editing a Text stack. None of the bottons at the top or the bottom of the Edit window are working — excerpt the three alignment buttons in the middle of the top.The good part is, that there are equivalents for many of these buttons in the menus, but the blue “Confirm” button at the lower right corner does not work either. I had to click on a different stack to close my Edit window and keep my changes.
Ah yes, good catch! I’ve tested that here and it does appear to be broken on Stacks, the Styled Text page style works. Anyway, we’re looking into the issue now. Hang tight!
It’s great to see that you’re still looking after RapidWeaver Classic. The issue with W3C validation has been around for a while; unfortunately, errors are still appearing after the update—for example, in the case of iTunes. Here is the link to the feed: Auf den Hund gekommen!
@KJM, Okay, so after further investigation this one turns out to be in the Stacks plugin rather than RapidWeaver itself.
On newer versions of macOS an empty toolbar container in the Stacks text editor sits on top of the buttons and swallows the clicks, which is why everything except the alignment buttons stops responding. Cmd-Enter still works to confirm, as do the menu bar equivalents. We’ve sent the details and a suggested fix to YourHead, so it should be sorted in a Stacks update.
I’ll leave @Isaiah to drop an update here on it’s progress and ETA!
Sorry, Dan, I don’t agree. I restored RWC 9.6.8 from my TimeMachine Backup and found there all the buttons on top or bottom of the Edit window working (in macOS 27.0.1) without any problem. So Stacks is not the culprit — you have to find the cause of the bug in RWC 10 beta.
@KJM Hi Kurt, the difference is in how each version was built. 9.6.8 was compiled on an older version of macOS against an older SDK, so it picks up the old behaviour and the Stacks buttons work. Classic 10 is built with the latest Xcode against the current macOS SDK, and that changes how the Stacks text editor’s toolbar behaves, which is why the buttons stop responding.
So it really is something that needs changing in the Stacks plugin rather than in RapidWeaver itself. We’ve sent YourHead the details, so it should be sorted in a Stacks update. In the meantime, Cmd-Enter and the menu bar equivalents still work.
Good luck with an update of Stacks 5. Yourhead Isaiah is busy with an other project. I have read there will be no more updates of Stacks 5. Hopefully, he will change his mind.
I emailed Isaiah at YourHead directly on Wednesday (as the support email now bounces), I’m waiting for a response and as soon as I get a reply I’ll update everyone here.
I’ve not heard back from @Isaiah yet, but I did managed to get in contact with @joeworkman and he’s going to pass on the information to Isaiah, so fingers crossed.
I’m a bit confused. How do I get the beta updates for Rapidweaver Classic if my subscription has expired? If I click on the Renew button within Rapidweaver Classic I just see options for purchasing Elements.
I’m sure Elements is spectacular, I just don’t have the need or bandwidth just now to learn a new program so I’d like to keep Classic in my toolbox for at least a little longer.
