Batch publish/unpublish whole trees

Bettina Braesch-Andersen

Vote:

I think I´ve seen this request somewhere but cannot find it. But will there be any such feature in the future?

Batch Unpublish a whole tree would be extremely useful since I've "inherited" a huge website with lots of so called "archived" roots that still are published and still found by the search engine. I do not want to remove them yet AND by some reason ordinary archive routine is disabled (I at least think there is such a thing as archive feature).

Batch publish is very useful when you do new websites or big updates. You cannot handle 100 of documents one by one then.

#32415

Sep 02, 2009 9:36

Vote:

Thanks for the input, we're currently looking into such a feature since it's one of the more frequently requested ones.

#32732

Sep 15, 2009 11:11

David F.

Vote:

Any update on this feature? Is it now possible to stop publishing multiple pages at once in CMS 5 or 6?

SEO: node, pages, child

#49270

Mar 11, 2011 0:34

Tobias Nilsson

Vote:

Hi David,

It is possible, but you will have to code it yourself. You could create a admin plugin that lets users pick a page in the page tree and then iterate through the children publishing them if not published.

PageDataCollection pdc = DataFactory.Instance.GetDescendants(YourPageReference);

foreach page in pdc:

DataFactory.Instance.Save(page, EPiServer.DataAccess.SaveAction.Publish);

Should be fairly straightforward.

#49275

Mar 11, 2011 10:07

David F.

Vote:

Thanks for the fast answer! I will try this out.

#49283

Edited, Mar 11, 2011 11:44

Janne Laineberg

Vote:

Hi! Is there a way of unpublishing whole tree as well?

#54445

Oct 17, 2011 9:18

Anders Hattestad

Vote:

Use the same code as above but do it rekusiv for all childs

#54446

Oct 17, 2011 9:49

tym.lawrence@netcat.com.au

Vote:

Is there any update to this thread - for instance has the feature been added somewhere to the product that is not obvious? Its something that would be really useful for large sites.

#71040

May 07, 2013 23:06

Linus Ekström

Vote:

Hey Tym!

We know that this is a often requested feature and actually planned and partly implemented this in the EPiServer 7 release. Due to time constraints we had to abandon/hide this feature for the release but I hope we can continue developing this support in a near future though nothing is decided at the moment.

#71043

May 08, 2013 7:44

Alexander Arques

Vote:

What's the status of this feature Linus, any progress?

#80148

Jan 15, 2014 17:12

Linus Ekström

Vote:

We have actually done some more research about this lately though nothing has been decided yet but I hope that we can release something in this area later this year.

#80168

Jan 16, 2014 7:55

Janne Laineberg

Vote:

This would be a really adequate solution in EPiServer CMS 7!

#80169

Jan 16, 2014 7:56

Manuel Donoso Soare

Vote:

How is that research coming? Our editors are screaming for this feature.

What about this solution:

http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=80831&epslanguage=en

Jr.

#81767

Feb 26, 2014 9:25

Linus Ekström

Vote:

The feature still has very high priority and the idea is to implement it as a part of a bigger theme that we recently started working on. Still can't tell you any dates but we will publish more information about this as it starts to evolve...

#81801

Feb 26, 2014 16:13

Manuel Donoso Soare

Vote:

Thanks Linus,

Thats great news.

#81803

Feb 26, 2014 16:18

Linus Ekström

Vote:

For any of you that have missed this, we have started to release part of this support through a feature named "Projects". It's still in beta and we are continously adding more functionality to this:

http://world.episerver.com/Blogs/Magnus-Stalberg/Dates/2014/8/Projects-Beta/

#90920

Sep 22, 2014 13:56