[MGNLACTIVATION-85] Do not activate pages already active Created: 04/Jun/14 Updated: 23/Sep/14 Resolved: 22/Sep/14 |
|
| Status: | Closed |
| Project: | Activation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.1 |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Teresa Miyar | Assignee: | Evzen Fochr |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Release notes required: |
Yes
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Although this feature will have to take into account we can't assume that page is in a same state on public just because it has green activation status (e.g. import or clone or manipulation via unwrapped jcr api) so whatever we do, it still has to be possible to activate even the page that is marked as activated Added option to publish only unpublished or modified pages, while Publishing pages incl. subnodes. To turn on this feature add new property to node cofiguration>modules>pages>apps>pages>subapps>browser>actions>activateRecursive - new property modifiedOnly with value true |
| Comments |
| Comment by Magnolia International [ 06/Aug/14 ] |
|
What's the reasoning ? |
| Comment by Christian Ringele [ 06/Aug/14 ] |
|
The reason is, that if you activate a tree recursively, and 50% of the pages have already been activated and status is "green", activation would be 50% faster. |
| Comment by Jan Haderka [ 12/Sep/14 ] |
|
While the code change itself looks functional I have following issues with the ticket as a whole:
|
| Comment by Jan Haderka [ 12/Sep/14 ] |
|
BTW there is also assertEquals |
| Comment by Roman Kovařík [ 22/Sep/14 ] |
|
QA: it's possible to use modifiedOnly property with non recursive activation, but it's not reflected. |