[MAGNOLIA-3091] Avoid logging unnecessary error messages during activation Created: 18/Feb/10  Updated: 16/Nov/10  Resolved: 16/Nov/10

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.2.3
Fix Version/s: 4.3.2

Type: Improvement Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3197 Better error message when the parent ... 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)

 Description   

in two cases:

  • when attempting deactivation of the content that doesn't exist on the public, ugly stacktrace appears in the public log file
  • when attempting to activate node without uuid (still possible, by path), the author logs bunch of errors on attempt to retrieve content uuid


 Comments   
Comment by Jan Haderka [ 16/Nov/10 ]

This issue has been fixed by fix for MAGNOLIA-3197.

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