Weâve been working on RapidWeaver 7.2 for a few months now, and itâs finally ready. We honestly think this is the best, most stable version of RapidWeaver yet.
If youâve not tried out RapidWeaver 7, you can download a free trial from our website. If youâre already using RapidWeaver 7, just launch the current version and youâll be prompted to update for free.
You can download this and other versions from the releases notes area at the knowledge base.
Whatâs New in 7.2?
Improved preview speed, preview status now displays at the bottom of the sidebar
Fixed an issue where RapidWeaver would sometimes crash on export/publish
Re-written Theme Browser for improved performace and relaibility
Fixed an issue where right-clicking in the sidebar would cause a crash
Potential fix for a crash when closing a document
Removed Autosave support as itâs causing more problems than it should be. Boo!
Fixed a super bad bug that caused data loss within the blog plugin
Fixed an index âout of boundsâ error that would sometimes appear on export
Other under the hood improvements and memory management changes
Pressing Done in the Advanced Settings sheet no longer causes a crash
Potential fix for reported issues when saving and closing a document too quickly
Fixed an issue with the %banner_path% macro outputting incorrect resource paths
Fixed an issue where RapidWeaver would re-upload all resources on every publish
Fixed an issue where editing the âprefixâ area in the sidebar would cause a crash
Fixed an issue where RW would upload all blog pages if the blog was the index page
Fixed an issue where the blog categories would sometimes not be exported
Fixed an issue where the wrong URL would be used for CSS files on the Blog Archive page
Fixed an issue where the advanced settings sheet wouldnât hide
Fixed a crash that would happen when opening a document with a missing theme while the Add Page menu is being shown
Fixed some layout issue with the page inspector
Plenty of other under-the-hood refinements and fixes.
I do know Yourhead came out with another PlusKit beta, I believe it is up to b6 now. You can sign up here to get access to it http://slack.yourhead.com
i knew better then to install a new update - they always seem to have issues ⌠luckily i had a backup with the old version and backed out the new. i just donât have time for this âŚ
Iâm using this update with no issues that I can see so far. Publishing is fine. Not using PlusKit. Got rid of that before this update because I had too many problems.
I am unable to update - I get an error message saying I am running Rapidweaver from an optical drive or somesuch and to move my RW7 into the Applications folder. But it is in the Applications folder!
@dan Well, I finally took the leap to RW 7 and so far 7.2 seems remarkably stable and publishing is working fine. Great work and much appreciated!
I did notice one possible very minor but annoying little bug though - if an HTML5 audio stack is set to autoplay it of course starts to play in preview, but now in RW 7 it continues to play when I switch back to edit mode and as far as i can tell there is now way to stop it playing in edit mode - it will continue to play until you open a different page in preview. In RW 6 the audio would stop playing in edit mode. This happens with both JWâs HTML5 audio stack and Stacks4Stacksâ Playlister.
@dan: Iâm happy!!! Finally!!! 7.2.1 solved my problem!!! On both project. It is a nice Christmas gift and I did not expect it. Thank You!!
âŚnow some more testing on RapidBlog and RWML in this version and I can dump all older RW versions on my hard drive!!!
Is anyone having difficulty with the the Stacks Library in 7.2.1? When I select the library icon, it flashes for a second then closes â every time. Cannot get it to stay open long enough to read it or make a selection.
No problems with Library icon here. Works perfectly fine. My guess is this is due to some specific in your setup, but I have no idea what is causing this. You may want to get in touch with @isaiah directly. He likely wonât help you today, but tomorrow onwards he can give you some good hints about what to do. He may already know about the problem with some folks. All I can say is it isnât a general widespread problem.
uh I am running into problems with formloom3⌠now my pages show me âCREATED WITH DEMO VERSION OF FORMLOOM 3â though itâs registred. Anybody else with same issue?