RWC wants to update. Does the new version have an Elements nag screen?
1 Like
It sure does, but you can simple check the “Don’t remind me” checkbox.
We’ve done a lot work on the publishing engine in the 9.6.x branch of Classic, so if you were previously having publishing issues we’d highly recommend everyone check it out.
Since the 9.6 updates we’ve had users report that publishing in Classic is now faster than ever!
P.S. We don’t check-in here very often these days, so if you want super swift answer to your RapidWeaver based questions, you know where to find us…
Happy Weaving!
The check-box is a great option, I wish more software had it.
Cheers.
We can get rid of the nag screen but a “Learn About Elements” still appears in the drop down list under Rapidweaver Classic in the top left menu. Can’t get rid of that? After the update I have still experienced a crash when publishing. Admittedly I have a large site and slowed down the upload to 3 connections. It still crashes - the program closes down and I lose all my work. I’m having to save the project after every change. So I am not sure whether the "lot work’ has been fully effective. Thank’s for the update, anyway.
No, the menu item is there to stay, but hopefully it won’t get in your way.
Sorry to hear you’re having issues, we’d love to get this fixed for you. Have you submitted a crash report for it?
We did recently add an Auto Save feature under General Settings that you might find useful:
Hope that helps, and do let us know about the crash report.
1 Like
@RapidWeaver Thank you for your reply. Next time it crashes I will submit a crash report. i have done so in the past. I have also included a screen shot of RW running in the Actvity Monitor while I published a project this morning under V 9.6.3. You will see that the %CPU runs at around 100% while publishing. I have a Silcon Mac Studio with 32GB of Memory. To me it seems to consume a lot of %CPU when publishing. Is this normal?
Thanks for the information on auto save.
What you’re seeing is actually expected behaviour. When an app is performing a heavy task like exporting or publishing, macOS will give it as much CPU time as it requests. So seeing RapidWeaver running close to 100% during publishing is normal, it means the app is using all available performance to get the job finished as quickly as possible.
As soon as the task is complete, the CPU usage will drop back down. In other words, high CPU while publishing is not a sign of a problem, it’s just the system letting RapidWeaver get the work done efficiently.
If you have any more questions about RapidWeaver, feel free to head over to our support Forum (you’ll get quicker responses that way).
Thanks for your reply. I just updated to Taho 26.0 this morning and opened RW 9.6.3. It crashed. I have sentr through the log report.
Thanks for reporting the crash. Unfortunately it’s a crash in the Stacks plugin, so we’ll need @Isaiah to take a look at this one.
I’ve forwarded the full report to YourHead, you can email support@yourhead.com for an update.
