[MGNLRES-324] Manually remove outdated JCR hotfix overrides Created: 11/Mar/19  Updated: 03/May/22  Resolved: 03/May/22

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLRES-323 Automatically remove outdated JCR hot... 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)
Date of First Response:
Epic Link: LD2021
Team: Nucleus

 Description   

User Story:

As a developer or administrator I want to find and manually remove JCR hotfixes, so that the resource changes that are in my modules and light modules resource files take effect as expected. 

Problem Details:

A common problem is that developers override a file-provided resource (for example a YAML app definition) in AdminCentral Resources app by "editing it" which creates a JCR item, a "hotfix". This JCR Item overrides the YAML file. So far so good. The problems come next:

  • Development team then makes a change to the YAML app definition, these changes are not reflected on the website. Why? (Oh yeah, that file is being overridden.)
  • What is the best route to discover those hotfixes and remove them?

Suggested Solution:

  • Resources App Filter
    • A checkbox "Show JCR Overrides only". Shows items with JCR origin which are actually overriding another origin.
  • Resources App Action
    • Archive JCR Overrides (naming?)
      • Removes on Author and Public.
      • Creates a backup file of them, in a directory with a timedate stamp.


 Comments   
Comment by Roman Kovařík [ 03/May/22 ]

The resources app can filter JCR resources only since Magnolia 6.2.

Generated at Mon Feb 12 06:49:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.