Frequently Asked Questions
This in-depth FAQ is broken down into sections and should answer the most commonly asked questions about RapidWeaver Classic and the forthcoming RapidWeaver Elements. If your question is not answered below, head to the RapidWeaver Community.
You can continue to use RapidWeaver 8 for as long as you like. Upgrading to RapidWeaver Classic is optional.
There are many features and fixes that have gone into RapidWeaver Classic. Best of all, it's 100% compatible with all your existing projects and addons, including stacks.
RapidWeaver Elements is not due until later this year, and when it is available, it will be in beta for some time. For now, we recommend all users upgrade to RapidWeaver Classic and enjoy the many benefits it brings, as well as looking forward to updates in the coming months.
We will offer discounts to all RapidWeaver Classic customers that want to purchase/upgrade to RapidWeaver Elements upon its official launch.
We're now building two versions of RapidWeaver.
RapidWeaver Classic is the next big release of RapidWeaver, so in essence, you can think of it as RapidWeaver 9. It's the same RapidWeaver you know and loves. It's compatible with everything (including Stacks), and it also has many new features and enhancements.
We're also building RapidWeaver Elements, this version of RapidWeaver is a massive departure from what we had previously planned. RapidWeaver Elements will launch as a beta later this year.
RapidWeaver Classic requires macOS 10.14 or newer.
Yes, if it worked with RapidWeaver 8, it will work with RapidWeaver Classic.
Yes. All plugins, themes, stacks, and projects work in RapidWeaver Classic.
Yes, ALL RapidWeaver 8 projects are 100% compatible with RapidWeaver Classic.
When you open an existing RapidWeaver 8 project it will be upgraded to a RapidWeaver Classic project and saved as a copy with the extension .rwc — your original project will not be modified.
Once you've upgraded a project you should remember to always edit and work on the newer one with the .rwc file extension.
Just like most software, newer save files are not backwards compatible.
So while RapidWeaver Classic will open RapidWeaver 8 files, RapidWeaver 8 cannot open RapidWeaver Classic files.
We have no plans to release RapidWeaver Classic on the Mac App Store. This may change in the future should the demand be there for it.
RapidWeaver 8 and RapidWeaver Classic both use the same bundle ID so when a user upgrades, everything (including addons) will continue to "just work". If we changed the Bundle ID users would have to re-select or migrate their addons (and this can be tricky for novice users). We wanted to make this upgrade as seamless as possible for all users.
Yes, we will continue to update and maintain both versions of RapidWeaver going forward. We hope this gives you confidence in our commitment to RapidWeaver.
This means you can safely continue to maintain and build new projects in RapidWeaver Classic and Stacks for the foreseeable future.
Yes! RapidWeaver 8, RapidWeaver Classic, and RapidWeaver Elements can be installed alongside each other and can even share the same addons folder.
RW8 and RWC share the same bundle ID and the Finder uses that to populate Launchpad. We did this so it was easy for users to upgrade, if we change the bundle ID, Sandboxing prevents the new app from accessing the same files/resources/addons - it’s a bit of a nightmare for users upgrading.
The Finder picks the newest app with the same bundle ID, so in this case, it will choose RWC.
Both apps are still installed on your Mac and can be found in the Applications Folder. There is no issue running them side-by-side.
YES! RapidWeaver Classic is a Universal app and compatible with both Intel and Apple Silicon-based Macs. To take advantage of RapidWeaver on M1 Macs, you’ll want to make sure all your plugins are up-to-date. If some of your installed plugins are not Universal, they will not run in the native version of RapidWeaver. If a plugin isn't compatible with Apple Silicon you will see the following error:
RapidWeaver Failed to load some plugins
PluginName: Couldn't obtain plugin principle class
To make older plugins (that are not Universal) run on an M1 Mac you'll need to install Rosetta for macOS. Apple has a guide on how to install Rosetta. Along with information on how to enable it on a per App basis. However, by running RapidWeaver under Rosetta, you'll lose some of the huge speed improvements M1 chips can bring. Please check with the developer of any plugins you're using to see if they are available as Universal builds. If they are not available, we'd suggest looking for alternative plugins and stacks that can cover the features you're missing.
Ideally, you'd always want to add code or make any changes in the project and re-publish the website. That way, the RapidWeaver project is the master file. In theory, you can edit the HTML/code once it's been exported. However, your changes will get wiped out the next time you upload your website from RapidWeaver. If you're wondering about the best way to do something, you can always get help on the RapidWeaver Forum. It’s always best to make changes in the original RapidWeaver project file where possible. It’s always best to make changes in the original RapidWeaver
In the past when we've seen file corruption issues (or missing images) when the user is running a utility or “cleaner” that has noticed a large cache directory and decided to “clean” it of images. Utilities like CleanMyMac, MacKeeper, and MacCleaner.
If these “Cleaner” utilities are run while RapidWeaver and Stacks are open, they can be aggressive when they see a large cache of images. Running these when RapidWeaver is closed is fine, of course – but removing cached images while RapidWeaver is open can affect the file's integrity.
We also recommend closing RapidWeaver overnight as some plugins store temporary images in the cache folder (and macOS can clear this out overnight) and cause issues in your Projects. Note: This is no longer an issue in RapidWeaver 9 and its built-in plugins.
Never use CleanMyMac, MacKeeper, and MacCleaner while RapidWeaver is open.
Yes, all RapidWeaver users will be offered a discount when buying RapidWeaver Elements. Remember, upgrading is entirely optional as we'll be supporting both Classic and Elements going forward.
RapidWeaver Classic is the RapidWeaver you know and love. It works with all your existing addons and projects.
RapidWeaver Elements is taking RapidWeaver in a new direction. It's built around the Elements Engine, our unique drag-and-drop engine. We'll be sharing more details and taking the wraps off Elements later in the year.
We are continuing to develop and support both versions of RapidWeaver, allowing you to pick the version that works best for you and your projects.
The Elements engine inside RapidWeaver has been built from the ground up utilising the latest web technologies, meaning it’s fast (like really, really fast!) and opens up a world of mind-blowing possibilities making it easy for anyone to build modern websites.
stacks are not compatible with the Elements Engine.
RapidWeaver Elements is still in development. We'll make an announcement regarding compatibility later in the year.
If you need to migrate projects or open older projects, but no longer have your license number, you can use the ones provided below.
RapidWeaver 7 Project files have a .rw file extension. RapidWeaver 7 licences are a string containing numbers and letters.
RapidWeaver 6 Project files have a .rw6 file extension. RapidWeaver 6 licenses are very long, and start with RMS.
RapidWeaver 5 project files have a .rwsw file extension. RapidWeaver 5 licenses contain three words separated by a dash.
RapidWeaver 4 project files have a .rwsw file extension. Licenses for both RapidWeaver 3.6 and RapidWeaver 4 start with RW3SN.
RapidWeaver 3 project files have a .rwp file extension. Licenses for RapidWeaver3.5 and earlier start with RWPL.
Use the following license to register a copy of RapidWeaver 3.5: RWPL.4408.58.1978.1891