[PUBLISHING-303] Investigate & POC. How the campaign publishing works Created: 12/Jul/16 Updated: 19/Dec/23 |
|
| Status: | Accepted |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Spike | Priority: | Neutral |
| Reporter: | Laura Delnevo | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 3 |
| Labels: | usability, ux-improvement-selected | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: | |
| Epic Link: | Publishing Page related content |
| Team: |
| Description |
|
| Comments |
| Comment by Antti Hietala [ 12/Jul/16 ] |
|
Concerns raised by had:
|
| Comment by Richard Unger [ 12/Dec/18 ] |
|
There are many more concerns for implementing this:
We've had to implement this functionality for a customer. It wasn't pretty. We restricted it to publishing DAM dependencies, in order to avoid dealing with the transitive dependencies. We publish unpublished parent folders along with the dependent items if needed. We display all the dependencies in a dialog, and allow the user to choose which ones should be published via checkboxes. If you ever implement this, and you're interested, we can give you a demo and talk about it. |