[MAGNOLIA-6528] Deleted resources are used as valid ones Created: 01/Feb/16  Updated: 14/Apr/23

Status: Open
Project: Magnolia
Component/s: configuration, resource-loader
Affects Version/s: 5.4.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
causality
caused by MAGNOLIA-6399 JcrResourceOrigin should not filter o... Closed
relation
is related to MAGNOLIA-6527 Deletion of a hot fix configuration i... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: deletionOfHotfix
Story Points: 2
Team: Nucleus

 Description   

To reproduce with an active subscriber:

  1. Apply a hot fix on a template
  2. Delete a hotfix (the node is marked as deleted)
  3. Try to use this template -> RegistrationException since the layered origin tries to use the deleted node as the valid template instead of delegating to next origin in the cascade.


 Comments   
Comment by Roman Kovařík [ 11/Mar/21 ]

I can, looks like we still don't filter nodes mark as deleted

https://git.magnolia-cms.com/projects/PLATFORM/repos/main.pub/browse/magnolia-resource-loader/src/main/java/info/magnolia/resourceloader/jcr/JcrResourceOrigin.java

Generated at Mon Feb 12 04:15:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.