[ALF-21423] First install of Alfresco 5.1.EA with Spanish Locale and Value 'Rep. Dem.' invalid filename Created: 29-Aug-15  Updated: 25-Mar-17  Resolved: 02-Oct-15

Status: Closed
Project: Alfresco
Component/s: Installer, L10N
Affects Version/s: Community Edition 201508 EA
Fix Version/s: Community Edition 201509 EA
Security Level: external (External user)

Type: Bug Priority: Blocker
Reporter: Angel Borroy (Inactive) Assignee: Closed Issues
Resolution: Fixed Votes: 0
Labels: PatchAttached
Remaining Estimate: 0 minutes
Time Spent: 5 minutes
Original Estimate: 0 minutes

Mac OS Yosemite 10.10.2

Attachments: File bootstrap-messages_es.properties    
Issue Links:
duplicates MNT-15026 In Enterprise 5.0.2 the first start c... Closed
duplicates MNT-14993 First install of Alfresco 5.0.2 with ... Closed
Patch Attached:
Date of First Response:
Resolution Time Custom Field: 4 weeks, 6 days, 9 hours, 56 minutes, 32 seconds


On a clean installation of Alfresco 5.1. Early Access, log produces

{{Caused by: org.alfresco.repo.node.integrity.IntegrityException: 07290001 Found 1 integrity violations:
Invalid property value:
Node: workspace://SpacesStore/c67bba8a-6b4f-4ee6-8d78-e7e276ab8b54
Name: Rep. Dem.




Constraint: 07290000 Value 'Rep. Dem.' is not valid as a file name. This property must be a valid file name.
at org.alfresco.repo.node.integrity.IntegrityChecker.checkIntegrity(IntegrityChecker.java:662)
And Alfresco does not start.

Comment by Angel Borroy (Inactive) [ 29-Aug-15 ]

It seems the problem is at community-edition/projects/repository/config/alfresco/messages/bootstrap-messages_es.properties

bootstrap.categories.cm_generalclassifiable.regions.asia.south_eastern_asia.lao.name=Rep. Dem.

Comment by Angel Borroy (Inactive) [ 29-Aug-15 ]

There were several "Rep." strings that has been replaced by "Rep\u00fablica"

Now Alfresco 5.1.EA is working

Comment by gbroadbent [ 10-Sep-15 ]

I have amended this file in the Repo bundle committed in HEAD rev111808

Comment by Richard Esplin [X] (Inactive) [ 01-Oct-15 ]

Angel Borroy says that he still sees this problem in the 5.1.b release.

Comment by Angel Borroy (Inactive) [ 02-Oct-15 ]

This is not a 5.1.b release issue: it's solved for this release.

Resolution field can be set to 5.1.b

Generated at Thu Aug 06 15:08:59 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.