[MGNLCDEP-84] List of pages referencing an asset is incomplete Created: 21/Jul/15 Updated: 15/Apr/16 Resolved: 27/Jul/15 |
|
| Status: | Closed |
| Project: | Content Dependencies |
| Component/s: | None |
| Affects Version/s: | 1.5 |
| Fix Version/s: | 1.4.3, 1.5.1 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: | |
| Sprint: | Sprint 3 (Basel) |
| Story Points: | 1 |
| Description |
|
Content Dependencies does not list all pages that reference an asset. To reproduce, try to delete dam:/travel-demo/social-icons/twitter.png in the demo. An alert says the image is used on 4 pages: /travel /travel/variants/variant-0 /travel/variants/variant-1 /travel/variants/variant-2 However, the image is used on every page of the site in the footer component. All referring pages should be listed to get a complete view of dependencies. |
| Comments |
| Comment by Federico Grilli [ 24/Jul/15 ] |
|
In this case the further depending pages refer that asset cause it is inherited from the footer area of the travel page. Unfortunately there is currently no info in JCR about whether an area is inheritable or inherited and, in the latter case, from where it is inherited. With that info we should be able to find the missing referencing pages but I'm not sure that we want to add more stuff in the pages hierarchy. What we might do, however, is displaying a more explicit warning message like If such solution shouldn't be satisfying I'd close the issue anyway as won't fix. |
| Comment by Antti Hietala [ 27/Jul/15 ] |
|
Let's improve the alert then. Slight edit to your wording:
|