Thanks guys,
I was about to visit Brighton earlier today and kick you up the bottom ( had to change this in the tone of a 1950’s comedy ) after hours of trying to update a site to v7.1.7 from V6.4 .
Seems like this update has sorted out the majority of problems on my end so far, still having preview problems.
Don’t relax just yet, I haven’t published yet !!

Hi Guy!
I agree this version of RW is quite good but I’am working on asite since few month and now each time I go to in the «Settings», «General», «Advanced…», do nothing else and click «Done» then «BOOM» I saw the window, that we don’t want to see «Something went wrong…

Is it just on my side or…

Thank you everyone at Realmac, your doing an amazing job byr the way!!!

Because of the crashing, I first turned on Autosave. BIG mistake. It crashed more. Then I got in the habit of saving every time I changed anything. RW started crashing on Save. RW crashes corrupted images, corrupted project files, corrupted installed stacks, and a few crashes corrupted the structure of my hard drive. I’m hoping and praying that the RW folks get it right this time!

Any plans to fix the “This document has been saved by another application” bug?

RE: Post #13
More specifically, it is the relative path to the fallback banner image that is buggy. RW7 is not including an extra …/ in the relative path on the individual blog pages - so it breaks the image path.

@jbob The same issue is occurring in every theme, not just mine. So changing themes isn’t going to fix the problem for you. The difference is that some themes apply RW banners as CSS backgrounds, whereas others use image tags. It’s only in themes using image tags that the missing image is most noticeable. But the fallback image will still be missing in themes that apply RW banners as CSS backgrounds, if you check the browser console. Either way, broken paths and missing images is no good to anyone!

The expected behaviour is quite simply that both fallback banner images should still be visible on the individual blog entry page. However the path for the %banner_path% macro is wrong, and therefore the image is broken.