DefaultHierarchyManager produces excessive amount of error messages
-------------------------------------------------------------------
Key: MAGNOLIA-3057
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3057
Project: Magnolia
Issue Type: Bug
Components: core
Affects Versions: 4.3 M1
Reporter: Jan Haderka
Assignee: Philipp Bärfuss
Fix For: 4.3
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 {noformat}
2010-02-03 10:56:01,182 ERROR info.magnolia.cms.core.DefaultHierarchyManager
: User not allowed to Read path [c820b390-2f19-43e9-915a-c544bda13a78]
{noformat} 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()}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
