I am trying to use Release Candidates as a way to make some major changes to my site and get stakeholder approval before publishing. Firstly, I wonder if this is a valid use of the feature?
So, I have created my RC by changing the site in the editor and I have Saved, but not published this version. I do a Preview and all looks well.
Then I go to Site > Create Release Candidate. Then I go to Site > Release Manager and choose the link to view my site which is something like http://mysitedomain/?siteRevision=260.
Firstly, I find that the menus are not showing the correct headings. They are not showing the headings from the Live site even...maybe some menu items I had many versions ago. The rest of the RC site looks fine and indeed if I make changes to the main text the changes show up OK. The menu just has the wrong titles. So then, I decide to do a hard refresh (CMD-R) a few times and after maybe 2 or 3 refreshes, the 'old'/currently published version of the site comes up. One or two more refreshes and I get the new RC site back (menus wrong still) a couple more refreshes and I get the old published site back and it stays that way.
I've tried this on Chrome, Safari and Firefox and the same thing happens. I've cleared caches and all.
This is all very weird. I'm wondering if the Release Candidate feature is ready for 'prime time' just yet? If not, that's fair enough. I'll make a different workflow for myself.
I just want to work on a 'development' version of my site, get it right, get approval and then publish it to the Live domain, replacing the old site. This must be a common thing that people want to do. Anyone have an alternative workflow for this if Release Candidates is not the way?
My site RC URL is
I will not play with it for a bit. The old version is coloured Orange and the New version coloured Blue. Easy to tell apart. I've also go the RC version set to 0% exposure.