[LIVECOPY-151] When pushing master content changes user should be able to auto publish content Created: 22/Jul/19  Updated: 17/Jun/20  Resolved: 02/Jun/20

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: 2.0.6
Fix Version/s: 3.2

Type: Improvement Priority: Major
Reporter: Mark Dainton Assignee: Chuong Doan Huy
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1h
Time Spent: 4d 3.5h
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by LIVECOPY-192 Publish include sub pages option for ... Closed
is cloned by LIVECOPY-196 Allow adding comment/date with auto p... Closed
Relates
relates to LIVECOPY-43 Add a "publish" button for each page ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: Live Copy Phase 2
Sprint: Add-Ons 38, Add-Ons 39
Story Points: 3

 Description   

When using the Push master content changes function it would improve workflow to be able to publish this content once the LiveCopy has been completed and the links automatically reconciled (see https://jira.magnolia-cms.com/browse/LIVECOPY-69 for auto-reconciliation functionality).

This change would greatly improve workflow and the ability of content editors to manage sites.

Request

When using the Push master content changes function users should be given the option to also publish the pages once:

  • LiveCopying has been completed
  • Links are reconciled to the local pages

Upon completion users should be shown a message to inform them that the pages have been published

 

PR:

https://git.magnolia-cms.com/projects/ADDON/repos/live-copy/pull-requests/46/commits



 Comments   
Comment by Laura Delnevo [ 28/Oct/19 ]

Thank you for your suggestion. We will take this story into consideration when we review the scope of the next phase of enhancements of the Live Copy feature

Comment by Marvin Kerkhoff [ 07/Nov/19 ]

Ususaly this should be an easy task if all functions are in commands it would be possible to chain this commands into one action on our own.

Comment by Marvin Kerkhoff [ 14/May/20 ]

Hi, i wanna add something to it, because we fall into this behaviour. In our scenario we had problems with CPU load and fall into serios performance issues.

  1. Create a live copy from a complete tree.
  2. Publish all referenced pages from the master tree somewhere inside the tree. To retrace this issue it is necessary that the parent node in the referenced tree is not published.
  3. The issue is now that the system will try to publish the referenced page and cannot do it. The thread seemed to be not closed until the parent page will be published. I don't know if this is a usualy behaviour also for all current publishings.
  4. In Live Copy this could end in a lot of these open threads because with such a publish referenced pages feature you can publish many pages with a few clicks.

Just keep this in mind if you ever develop a "Publish referenced pages" action.

Generated at Mon Feb 12 02:25:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.