"Publish including dependencies"

[Christoph Damm]

Hello,

I was wondering (well actually more imagining that i have seen this before) if there is a module/enhancement that would give something like a "publish including dependencies" functionality.

Most default case is author publishes page but not the changed/newly added assets.

The content dependency module is great and might be a precondition for such.

Anyone with an idea or am i maybe just too blind to see what i am looking for?

Thanks a lot and regards

Christoph

[Roman Kovařík]

Hi Christoph,

There is https://docs.magnolia-cms.com/product-docs/6.2/Apps/List-of-apps/Campaign-Publisher-app.html.

It's still pending migration to Magnolia 6 UI though.

Regards 

Roman

[Christoph Damm]

Hi Roman,

thank you for pointing that out. However, I don't think this is quite what is needed.

As this would mean creating a campaign for each page publish, which doesn't sound practical to me, if i understand correctly.

I'd rather look for a "publish including references" type of command possibly.

But I understand there is no such thing there yet, so I guess so far it's pure author responsibility to make sure everything is published in the right order? (ok and developer responsibility to code fail safe templates, which yet will result in not nice uis obviously if content is missing).

Is that a correct assumption?

Regards,

Christoph

[Christopher Zimmermann]

Hi Christoph,

This is an improvement that we currently consider adding to the product. Please see this card on the "Considering" phase of our backlog: https://portal.productboard.com/magnolia/1-magnolia-roadmap/c/58-publish-related-content

I would appreciate it if you can click on one of the buttons at the bottom which will give you a text box and you could describe your need, or problems you are having - and any input about how you would like it to work or expect it to work. Thanks!

Also, this module may be of interest to you "Content Dependencies": https://docs.magnolia-cms.com/product-docs/6.2/Modules/List-of-modules/Content-Dependencies-module.html

Topher

--
You received this message because you are subscribed to the Google Groups "Magnolia User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to user-list+...@magnolia-cms.com.
To view this discussion on the web, visit https://groups.google.com/a/magnolia-cms.com/d/msgid/user-list/CAGgPrdjZonhqZ2wU5_cur4z3cTGtoGuJ64j41m5Rh-fGoHD-gA%40mail.gmail.com.

--

Best regards,

Christopher Zimmermann / Product Manager 
christopher...@magnolia-cms.com 

Magnolia 
Oslo-Strasse 2, 4142 Münchenstein (Basel), Switzerland
Office: +41 61 228 90 00 www.magnolia-cms.com 
 

[Christoph Damm]

Hi Topher,

thank you a lot for your reply, sorry for my delay.

I saw and voted for the item in teh product backlog and will also schedule a call with Laura to provide more insights.

I added the content dependencies module already, this helps a bit to see at least dependencies, however I mainly added it to avoid deleting content which is still in use at another place.

Thanks again, and best regards,

Chris

[Richard Gange]

Hi Christoph-

We do have a module in the incubator which can help. See https://docs.magnolia-cms.com/workflow-extended-module/index.html. There is a feature call "Linked Resources Publication" which can find most dependencies. I think the only place where it cannot help is resources which are linked through the Rich Text Field. Since this is an incubator module and it relies on workflow you would need a license for it. 

HTH

Rich