[MAGNOLIA-7041] Publish incl subnodes can wipe out component variants on public Created: 23/May/17 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 5.5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
To recreate:
|
| Comments |
| Comment by Roman Kovařík [ 23/May/17 ] |
|
You should not use JCR Browser for activation, JCR browser is not aware of custom activation rules. |
| Comment by Frank Sommer [ 16/Jan/18 ] |
|
The JCR browser is a tool for admins and should activate every content node. It's irritating, if a variants node in a deep node structure is not activated or the variant node is removed from public instance. |