[PUBLISHING-38] Activation/deletion error after 5.6.1 update Created: 09/Jan/18  Updated: 29/Mar/22  Resolved: 20/Feb/18

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: 1.0.2

Type: Bug Priority: Major
Reporter: Viet Nguyen Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File error.log    
Issue Links:
Problem/Incident
causes PUBLISHING-53 Publishing Monitor switching informat... Closed
causality
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:
Sprint: Kromeriz 134, Kromeriz 135
Story Points: 1
Team: Nucleus

 Description   

Thanks to haddorp in SUPPORT-8274:

After migrating from 5.5.7 to 5.6.1 we have problems with the activation module when trying to delete a configuration node we get an error.

Please reference to 'error.log' attachment for more detail.

Problem caused by accessing the file publishing-core-backed-messages_en.properties.
"publishingMonitor.dateformat" is not found. So, the key instead of the actual value is used for the date formatter - and this does not work.
When putting a copy of this properties file on the class path it work. But I have to remove "_en" from the filename.
publishing-core/i18n/publishing-core-backed-messages.properties

Actually we just provided an '_en' file without fallback default one which easily cause issue to customers who don't use English as default languages.



 Comments   
Comment by Antti Hietala [ 25/Jan/18 ]

Fix the file name:

  • Remove the _en suffix. Don't need it for the default message file.
  • Replace backed with back-end. The intention here was likely to differentiate front-end (templating) labels from back-end (AdminCentral) labels.
Comment by Roman Kovařík [ 14/Feb/18 ]

Remove the _en suffix. Don't need it for the default message file.

We can't remove the suffix, the english translation would be then loaded to fallback locale translations (which could be e.g. german).
Removing the translation since it's the only translation for publishing monitor, doesn't make sence to support data format translation if nothing else is translated.

Generated at Mon Feb 12 10:34:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.