For some reason, an update to Site.com is not updating the version call for the css file.
Site.com forces the call to the css file in the head to have a version number. (eg,
/assets/css/styles?v=1234). This is obviously to force the browser to use the latest update to the css file.
It normally works, however this time it will not update. I've made three separate changes, published each time, but the call to the stylesheet stays at
/assets/css/styles?v=1147. If I manually load that sheet, and change the v parameter to 1148 or 1149, I see my changes. But again, I refresh and even load the page in a new browser, and still Site.com serves the stale css at
Is there a way to force this to update?