RW 6.3.3 exports always all my files even if I only change 1 small text in my project using Stacks 2.7.2, RW Contact form & Loghound Sitemap Plus 2.90.13. Switching back to RW 6.3.1 exports only the changed files and does not export my full project every time like RW 6.3.3
My only problem with the upgrade is a resource file refuses to upload. It takes some other resource file, a previous one version of the one I’m using, and uses that one. So odd.
I went into the site using Cyberduck to remove the old resource files. Then I entered RW again and Republished the site. Same darned resource file which no longer exists on the site is loaded onto the website. Completely frustrating and mystifying.
I confirm, the latest upgrades caused RW to slow down my workflow significantly. Loading and saving the project takes approx. five times longer than before. As one result, I deselected the Auto Save feature.
The issues we’ve been made aware of are publishing related. If you’re seeing performance degradation please could we be sent a copy of your Project file to investigate? There’s tools within Xcode we can use to pinpoint what’s going on.
There is definitely a problem with updating websites with RW 6.3.3. I’m experiencing the same problem that everyone is describing here. I make a very minor change to 1 page, and when I ‘publish’ the change, RW6 takes forever to make the change, going through what seems every single page in my site before it finishes. It takes five or ten minutes or even an hour sometimes. I’ve had no problems whatsoever with this until recently. It’s not a network problem! It happens regardless of which computer I’m editing from and whether I’m editing the site from home or work. Please fix this.
I also had the symptom of all my files seem to get a changed flag after updating to 6.3.3, so all files have been uploaded again when publishing.
Second publishing attempt was fine.
Just a quick update: it appears that when publishing a page (or indeed project) for the first time, RapidWeaver isn’t respecting the Smart Publishing status. We’ve been able to reproduce it, and we’re working on a fix. I’ll post a beta so we can get your feedback, and launch it to the wider user base ASAP once we’re happy it’s fixed the issue.