We shipped the ability to publish individual CMS items using the API. We're working on Zapier integration and a way to publish items in the CMS Collection UI.
can you all ALSO up-vote this one below. It just does not make sense that when publishing design changes to 1 domain, the CMS content gets published to all domains!
Ability to publish CMS content to specific Domains
in my humble opinion, this is a bug! again... prefixing it all with ALL DUE RESPECT to Webflow Team, which makes so many amazing things happen! I am grateful to you all but as a paying customer I would like this fixed!
Martha McMillan commented
31 Aug, 2020 06:12am
Single CMS Item is a very useful and beneficial thing for us. Webflow wishlist has been doing an outstanding and astonishing work in this regard and get uk essay service from qualified writers. Thanks for sharing this with us. Keep sharing more like this with us.
Matthew P Munger commented
22 Mar, 2018 05:05pm
This feature has shipped.
Markus J. commented
23 May, 2017 12:14pm
Ability to do that in the CMS editor urgently needed. Or how can I make use of the API – not without investing in programming, right?
Channing Hinton commented
12 May, 2017 09:06pm
I'm SO excited about this.
Channing Hinton commented
5 Apr, 2017 10:02pm
It would help if there was a one-click publish option via some sort of app or even a function call. If you could send a command to a site and publish without having to login, that would save a world of work across many sites updating via Zapier.
Stephen Lechner commented
10 Mar, 2017 09:00pm
Not being able to make simple text updates without re-publishing an ENTIRE site is extremely frustrating, especially if someone is working in designer and another team member is working in editor.
Daniel Mcleay commented
15 Feb, 2017 09:52pm
Voting for this, without this feature the api is useless in my opinion as it still needs someone to login and publish the site??? The Api should not have been released without this feature. I have invested money and time into getting a developer to build out a custom module for my company only for it to be completely useless as our clients still have to manually publish everything. Is anyone using the api? I think that many people will not without this feature.
Channing Hinton commented
7 Feb, 2017 09:24pm
Again, voting for this item. 100+ websites in the coming future all updating dynamically via Zapier so my clients can keep their sites updated themselves
Markus J. commented
18 Jan, 2017 07:15pm
Yes – there should be the option to 'Save & Publish' in addition to 'Save' for each CMS item. It would be a much faster way of working sometimes.
Lawcomm Solicitors commented
18 Jan, 2017 01:14pm
Or a single page. Any individual change basically i.e.
When you click the publish dropdown, it would show a list of every individual change not yet published for you to (de)select.
can you all ALSO up-vote this one below. It just does not make sense that when publishing design changes to 1 domain, the CMS content gets published to all domains!
Ability to publish CMS content to specific Domains
https://wishlist.webflow.com/ideas/WEBFLOW-I-12
in my humble opinion, this is a bug! again... prefixing it all with ALL DUE RESPECT to Webflow Team, which makes so many amazing things happen! I am grateful to you all but as a paying customer I would like this fixed!
Single CMS Item is a very useful and beneficial thing for us. Webflow wishlist has been doing an outstanding and astonishing work in this regard and get uk essay service from qualified writers. Thanks for sharing this with us. Keep sharing more like this with us.
This feature has shipped.
Ability to do that in the CMS editor urgently needed. Or how can I make use of the API – not without investing in programming, right?
I'm SO excited about this.
It would help if there was a one-click publish option via some sort of app or even a function call. If you could send a command to a site and publish without having to login, that would save a world of work across many sites updating via Zapier.
Not being able to make simple text updates without re-publishing an ENTIRE site is extremely frustrating, especially if someone is working in designer and another team member is working in editor.
Voting for this, without this feature the api is useless in my opinion as it still needs someone to login and publish the site??? The Api should not have been released without this feature. I have invested money and time into getting a developer to build out a custom module for my company only for it to be completely useless as our clients still have to manually publish everything. Is anyone using the api? I think that many people will not without this feature.
Again, voting for this item. 100+ websites in the coming future all updating dynamically via Zapier so my clients can keep their sites updated themselves
Yes – there should be the option to 'Save & Publish' in addition to 'Save' for each CMS item. It would be a much faster way of working sometimes.
Or a single page. Any individual change basically i.e.
When you click the publish dropdown, it would show a list of every individual change not yet published for you to (de)select.