Classics website files won't open now

RapidWeaver Classic
1

I have used Rapidweaver for many years. This morning I got a frantic message from one of the nonprofits I design and host their websites. None of the websites are active now and I can’t even get the projects to open in Classics to attempt a republish. I upgraded to the latest version 9.6.8 awhile back and uploaded changes without any issues and the websites were functioning then. HELP!!!

UPDATE: I have contacted the new hosting company and the websites are online again. But I still can’t open the files from Rapidweaver Classics to do changes for the nonprofit. When I click on the files either from the folder where I have them stored, or from Rapidweaver, neither will open them up.

2

Glad that worked with sites up…

Dan mentioned to another to re enter the serial number

3
4

Thank you, I deactivated and reentered the serial number…now it’s working! Whew, your response is much appreciated.

5

No problem :wink: happy to help :slight_smile:

6

Hi guys,

I have a similar problem with Rapidweaver 9.6.8 and some of my RW sites…

Here’s what happened: I added a page to an existing (large) site and attempted to save (cmd+S)

RW locked up and had to be killed with force quit.

Now that site will not load in RW - it starts up but never loads. A couple of my other sites experience the same problem but some do open successfully, suggesting to me that it may be a 3rd party plug-in that has somehow become corrupted.

What I’ve tried - starting RW with option-click and unchecking all boxes, rebooting MacBook pro, reinstall RW 9.6.8, deleting /Users/Steve/Library/Containers/com.realmacsoftware.rapidweaver folder…

No log file is produced in /Users/Steve/Library/Containers/com.realmacsoftware.rapidweaver/Data/tmp so can’t see what is causing the problem.

Can anyone help please? This is affecting my ability to service my customers. Thank you

7

Hi @SJRNet

What was the page type you added before the project file locked up?

Try this:

Right-click on the project file >> Show Package Contents

show-package-contents-1
show-package-contents-11156×906 92.6 KB

Then delete the RWUIState.plist file.

show-package-contents-2
show-package-contents-21260×864 74.6 KB

Let us know how you get on.

8

Hi Dan,

Thank you so much for getting back to me on this so quickly! :slightly_smiling_face:

The page I added was a clone of an existing stacks page, which I renamed and altered the content.

I tried deleting the RWUIState.plist file, as you suggest, but the RW site is still not loading.

I will try again after a reboot and get back to you…

Thanks, Steve

9

Probably something on that page then, which Stacks version are you using and which macOS version are you on?

10

I am on MacOS Sequoia 15.7.5 (24G624)
My Stacks version is 5.0.0

This time, RW failed after hanging a while, so I have submitted the report under my email address steve@uksoccerleagues.com

11

Seems like that’s an older version of Stacks. Can you try to download the latest version 5.3.3b1 here Downloading Stacks Beta and see if that helps? I know there were some problems with older Stacks versions in RWC 9.6.8 on newer macOS Tahoe releases…

12

Sadly, that didn’t work either. RW just hangs at this point:

image
image902×346 49.3 KB

I have tried restoring the RW site from Timemachine backup from a few days ago, when I know it was working, but that won’t open either.

Are there any files that I can send you to look at please Dan?

Thanks, Steve

13

Sure thing, send the project file and your addons folder over to us at support@realmacsoftware.com and we can take a look.

14

Hi Dan,

I have shared the files with you via dropbox - email sent with link.

Thanks, Steve

15

Hi Dan,

I have finally managed to fully recover this project by getting Gemini-CLI to investigate.

I am sharing the findings with you here in case that helps you with any other similar issues:

✦ The comparison reveals the “smoking gun” for the hang.

The Real Cause: Corrupt Security-Scoped Bookmark

The original project bundle has an extended attribute that the new one does not: com.apple.security.private.scoped-bookmark-key

This attribute is a “bookmark” used by the macOS sandbox to grant RapidWeaver permission to access files within the bundle or resources linked to it.

When you cloned the page and hit Save, RapidWeaver attempted to update this bookmark. Because the operation hung, the bookmark became stale or corrupt. Every time you tried to open the project afterwards, RapidWeaver asked macOS to “resolve” this bookmark. As we saw in the process sample earlier, the app was getting stuck indefinitely waiting for the scopedbookmarksagent to respond to this specific, broken key.

Other observations:

1. Structure: The original bundle was missing the Resources and SharedPluginData folders (because we had moved them out), but even with those gone, it still wouldn’t open. This proves the issue was at the bundle level, not with the internal files.

2. Dropbox Attributes: The original also had several com.dropbox.* attributes which can sometimes conflict with macOS’s own file locks during a save operation.

3. Quarantine: The original had a quarantine level of 0083, while the new one is 0082. This indicates the OS was treating the original bundle with a higher level of suspicion/restriction.

Summary

The hang during the Save operation created a “deadlock” in the macOS security metadata attached to the folder. Since this metadata is attached to the folder itself,

simply moving files in and out didn’t fix it. Creating a brand new folder (which doesn’t have that corrupt scoped-bookmark-key attribute) was the only way to break the deadlock.

Thank you so much for your assistance with this, Dan - it was much appreciated.

Best regards, Steve

16

RapidWeaver Classic projects (macOS bundles) can hang indefinitely on open due to a corrupt ‘com.apple.security.private.scoped-bookmark-key’ extended attribute.

The fix is to create a fresh bundle folder and move the internal project data into it, which clears the deadlock. :slightly_smiling_face: