Hi Community,
I have collaborators who have made changes to their site and when they publish the live site still displays previous images and text. Any insight would be greatly appreciated!
Here is the site link below!
Here is my site Read-Only: LINK
(how to share your site Read-Only link)
Is still still a issue? Webflow changed a lot of things the last couple of weeks. @webdev do you know if Webflow has changed something like a flag when a site is published or not? Now that people can edit live items. As I kick of a make.com process only after a site wide publish and I also had a complaint from a client that some changes where not reflected live.
CMS item publishing changed.
When you create an item, it defaults to Draft state, and when you edit an item the changes are in a Draft changes state.
This has nice workflow advantages when you’re working on content like blog edits, you have a ton more freedom to make those edits over time without impacting the production site.
BUT, it’s also quite confusing for people who aren’t used to the extra publish step.
If the client is using the designer edit mode, they need to click Draft changes at the top and Publish now when they’re ready for that change to go live.
Note, if they’re using the Legacy Editor - I have no idea if it’s been updated in a similar way. They may just be stuck and have to call you to publish those items.
My thinking is that the change is great, but the default-draft-state and the UI is quite confusing, both for long-time users and for new users, it’s just not intuitive having two publishing paths. It gets especially confusing if you edit both CMS item content and CMS template static content, because then you need to publish both the item and the site, separately.
I describe that situation here- it’s easy, just requires a new way of thinking in your publishing processes.
My understanding is that they can create / update live items even without hitting publish at all. Its also more about when you have a automation running.(So no need to call the designer for publishing) (They can also hit the site wide publish, the button is still there.
The items go online but there is no site wide publish in a sense there was before. That is in the legacy editor mode, at least that is what my client told me, and after having a quick look in the options there is a publish option for a single item bypassing a site wide publish.
For some automations in make or zapier that could present as a problem when the automation trigger is looking for a site wide publish.
Hi Patrick,
The primary difference now is that CMS item changes default to a “draft changes” state, and new items default to a “draft” state.
Until you update that to “Publish now” or “Stage changes”, a site wide publish won’t publish those CMS changes.
