Hi All
This is a very, very tough bug to crack… I have encountered it myself and tried to find a reproducible set of steps to make it occur, have sent multiple crash logs, multiple Console logs, sample projects… it is always data corruption, but what is causing the data corruption is turning out to be extremely difficult to find and to make steps to replicate to fix it (I don’t work for RMS but am trying to isolate the issue from a steps to replicate point of view!).
Solutions I have found to make the issue go away for a while (by awhile I mean a month of steady use) is to make sure you try these steps, any combination of which often temporarily fix the issue.
A. Close RapidWeaver & Restart RapidWeaver (Update any plugins if prompted - often the prompt will go to the background on site launch so check your Window to see if there are any updates the background) and repeat step A.
B. Create a new project with just a stacks page in it, save it (This will be your test project always without affecting live sites), now go into Stacks and update all your stacks if you have any out-dated. Save the project again and perform step A.
C. If Steps A and/or B do not resolve the issue then restart the Mac (This effectively kills any temporary files that may have been built up by opening and closing project files and/or multiple page views within RapidWeaver). Start RapidWeaver once your system is fully launched (Dropbox, etc have synced) for best reliable results.
D. Always launch RW with the project created above, check for updates, save the project and close the project. If the project fails to save then you’re not messing with a clients site data and repeat steps A through C again.
This isn’t a fix, but until we (the users of RW) find reproducible steps to replicate the issue, there is only so much @nikf can do to troubleshoot this issue.
I know it is a PITA, but it’s something we have to do until the issue can be reliably reproduced so it can be fixed. No reliable reproducibility means no fix.
HTH
Brad