I notice an inconvenient behaviour but wasn’t sure if it was a bug or not.
I was working on a client project update and made sure my publishing targeting options were set on my staging .webflow.io subdomain for testing purposes with the client.
I didn’t publish it anyway but my client called me saying there was some changes on the live website.
It appears that publishing from their editor/CMS also published my changes in the designer.
Even if I might have forgotten a setting somewhere, the client shouldn’t be able to publish design changes. It’s like all the changes data that are being pushed when publishing are shared between editors and the designer.
Anybody experiencing a similar issue and have been able to solve it? Or any feedback from @webflow on that matter?
Hi @Maximosaurus, at the moment, if the client does a full publish, this will also publish the design changes that exist on the site, both the webflow.io domain or the custom domain.
It is exactly what I needed to keep working on these updates in peace.
It would be nice to have some privileges control over what the client can publish from the editor on future updates though. The save dropdown publish button is not very intuitive for the client.
This is really, really, really, really… really, really, really BAD!
I just cannot believe that editors will have to publish other people’s changes in order to publish their modifications! (Only exception being CSM items.)
I mean, how can I sell this to an organisation? People will publish each other without knowing exactly what they are publishing? On top of it they’ll publish the Designer’s work in progress!?!? How can this be the case? How can Webflow not have come further in the years they’e built the system. This seems so rudimentary and wrong that the Editor should be considered as ‘private beta’ or something like that.
@cyberdave It’s been quite awhile that this feature has been requested, whereby Editors should be able to select where to publish their changes like Designers do:
Publishing options:
→ Custom Domain
→ Subdomain
I think there’s many of us who are using Webflow to work with big clients and organizations losing our clients bcuz this feature is lacking. What’s the dev team’s take on this? It’s really frustrating.
I just experienced this today. I had some major changes being reviewed for publish in the designer and one of our content editors published to the blog, which published all my changes. My changes were not supposed to go live till next week. Now I’m scrambling to fix it and hide all the links.
Not okay.
Changes to the CMS items and publishing from the designer should be separate actions, in my opinion. Our blog writers are not designers and the fact that they are publishing my unfinished work isn’t cool. Their post should publish independent from the work I’m doing.
I see there’s an option to publish a single post, but it’s hidden, and it’s hidden for the wrong audience for it to be hidden from.
Same here. I’m working on a website where only one page should be without a password. I’m publishing everything on the .webflow.io domain, but when the client is publishing (sometimes working at the same time) all the changes are being published on the main domain. This is so inconvenient because then I have to put a password on every page that shouldn’t be visible and publish it again.
To be honest, from all I read in the forums it seems that the quickest and immediate (really apply immediately Webflow!!!) is to remove the Publish button for the Editors. This would save us soooo much trouble and I personally don’t mind receiving a message from the editor when they want me to publish it for them. Yes, will loose some pressious 15 seconds, but I prefer it to wasting hours in trying to resolve all the mess that happens when someone new to this Webflow issues works with the Editor.
@Webflow - get rid of this Publish button in Editor NOW!
Yes, I also encountered the same problem recently when I joined a new company.
I tried to figure it out how to have a control over publishing on Editor dashboard, but didn’t got a solution for that.
Hiding the publish button will not resolve the issue where you have 10 collaborators.
Help me with something more efficient!
OH WOW, so simple yet so effective! Great great job thinking outside of the box @hayatbiralem and dumbing things down! I was here about to ask for some sort of settings page and some complex sort of permissions dynamic and here you are with a super clean and quick solution!
Scenario: Webflow is allowing a guest editor to edit a piece of content but not allowed to edit, let’s say the padding of that text box. Now if I’m in the designer and change the padding to that text box but am not ready to publish it yet…and then the guest editor hits “publish”, it publishes my change to the padding. How is this a thing? What if it’s a much more impactful edit than padding?
Isn’t this supposed to be convenient for a client to be able to go in and make changes to the content without needing to contact the designer/developer? Instead, there would still need to be communication with a client. The client would have to contact me and say “I’m about to publish, are you in the middle of any large site updates that haven’t been tested yet or are not ready to go live?”
For a client to think they are simply going in to change a “.” to a “!” and all of a sudden they publish a big update that’s nowhere near ready to go live?
Am I making the correct assumptions or am I missing something?
All I really would like to do is tell my client they can go in and add to a CMS collection and publish but have no other permissions. Is this possible?
Not sure that’s much of a solution. My clients want to point at a bit of text and edit on-page, no matter whether this is part of a static page or a collection. Your solution would mean they can’t publish any change to content on that isn’t held in a collection.
@cyberdave This does not work as you’ve explained. I clicked “Publish 1 change” from my CMS (Editor) account while Admin has some design changes in the pipeline. I was expecting only that one edit to get published, but even the design changes got published. This seems like a feature malfunction.
The whole editor workflow should be inspected thoroughly by Webflow, there are too many of these flaws, making it cumbersome to work with. I just don’t understand it, you have this beautiful UI where clients can work in the actual page without complicated login environments like Wordpress, and you don’t fix these kind of steps…
Hello Viena_Prasad. What was meant here is using the dropdown menu next to the green Save button when you are editing one item in the Editor. This will publish that item only (for example a blog post) and not push any changes from the Designer.
What you described seemed to be using the blue Publish button (that yes, says 1 change or as many as you have done on the Editor, but actually publishes the entire site).
Regarding this thread:
I guess Webflow can’t separate design changes made in the Designer from text changes made in the Designer or static pages. So, if one person is the designer changing the structure, and another the client either using the Admin account or the Edit to change text on Static pages, then to publish those changes you have to publish it all. I guess the solution would be being able to pick whose changes get published. But again, if this would be the case, if as a designer I change a text on a static page and then client changes it again, and the clients changes are supposed to go live but mines aren’t, does it or does not get published? I think it it tricky.
Regarding hiding the button: it was a neat trick, but it turns out that Webflow’s single CMS item publishing is failing, and our clients are loosing work they put in and disappears after being pushed with ‘Publish’ under the dropdown of the green Save button. As a bad short time solution, we figured out they should Save the item (green button) and then Publish (blue button) the entire site. This leaves us with no option to keep design changes from going live, just to give managers the power to publish their own CMS item changes and not loose their work.
Webflow please have a thorough look into this, it is a big problem.