[MGNLRES-342] Resources-app - displaying wrong resource origin Created: 25/Nov/19 Updated: 29/Mar/22 Resolved: 05/Jan/20 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | 3.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| 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: | |
| Team: |
| Description |
Context - Displaying the origin of the resourceIn the resources app, a resource's origin can be:
(1), (2) are frequently occurring. Reproducing the issue(s)Example scenario - part 1
The new resource(s) static/, static/lala.png and static/solala.yaml are all marked as origin from JCR. Example scenario - part 2 Now delete the created resources (/static/*) from above. (Currently you need the JCR app for this, see In consequence, the resource should be "back to normal", showing the same origin as they had showed at the very beginning of the scenario. For instance,
|
| Comments |
| Comment by Aleksandr Pchelintcev [ 05/Jan/20 ] |
|
The problem lies in the fact that the sample resources are deleted via JCR browser app, which is not intended way of working with resources: specific resource deletion action would also recursively erase the folder nodes in case no JCR resources are present in them any longer. In the described scenarios the hotfixed folder nodes remain, which is properly indicated by the UI. |