I’m having a weird issue with the Publishing as of yesterday - the changes I am making on the website in the design mode aren’t being published to the main domain, however, they are published correctly on the staging website.
I’ve found a very interesting issue here - as I’ve created a new CMS template, it published on the main domain successfully (it didn’t exist before), but as I tried to make any changes to the page - once again, the Publishing to the main domain isn’t doing anything, while Staging domain reflects everything correctly.
Seems like a very weird caching issue, but clearing cache/trying different devices doesn’t seem to help
Hi Dennis, you didn’t share your readonly designer link so I cannot check- but most likely you have edited a CMS item and it’s in a draft changes state.
I do have a few drafts, but non of them is in the “Draft Changes” State. I can try to remove all the drafts together today, but need to back them up first
No, you don’t need to remove drafts, just make certain that everything you want to be published from the CMS shows as published.
I can’t identify any differences between your staged and published sites currently- can you identify a specific problem?
My first guess here is that either your browser or your router is caching and you’re seeing old data- try accessing your site on your phone when it’s disconnected from wifi- you’ll be able to tell better if your changes are being cached on your network.
Additionally, there’s an exclamation point at the end of the sub-header and the “.” on the other version - I’ve highlighted these on the screenshots above
It’s very weird that you’re seeing the correct version. I’ve asked my team members to check it for them, as I was trying from multiple devices and IP addresses (even got myself a VPN just to check my sanity) - and it still shows the dated info.
They’ve just tested themselves and they also see an OLD version with the end of year special.
I’ve been using Webflow for more than 3 years with multiple projects and NEVER had to deal with this issue before
If you’re really covered a wide range of devices, networks & IP’s it sounds to me like a CDN issue on the server covering your geography.
I’d assemble a list of IP’s you’ve tested from and forward to support, it should help them identify the CDN server that’s having issues.
You could also try unpublishing and republishing the site, but there’s a very small risk that would bork things if something’s seriously broken.
As backup insurance, I’d probably clone the site just to ensure you have an intact version that you could transfer the plan to, and publish separately from your current one in an emergency.