[MAGNOLIA-3057] DefaultHierarchyManager produces excessive amount of error messages Created: 03/Feb/10  Updated: 03/Dec/13  Resolved: 03/Dec/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Philipp Bärfuss
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3058 AbstractNodeData#getReferencedContent... 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

 Description   

The AbstractNodeData.getReferencedContent() at some point calls hm.isExists() method passing in possibly uuid. The uuid is then evaluated as path by hierarchy manager and access permissions are checked, which leads to the error message like

2010-02-03 10:56:01,182 ERROR info.magnolia.cms.core.DefaultHierarchyManager    : User not allowed to Read path [c820b390-2f19-43e9-915a-c544bda13a78]

being logged.
This is quite obtrusive in the log files, specially so since STKUtil.getReferencedContent(), that invokes the above mentioned method in NodeData, is called quite often from templates.

The possible solutions are either to lower severity of the mentioned error message in DefaultHierarchyManager or to make sure that AbstractNodeData determines whether the string contains path or uuid by other means then calling hm.isExists().


Generated at Mon Feb 12 03:42:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.