[Archivesspace_Users_Group] PUI locales not being fully loaded in v3.1.1?

[Andrew Morrison]

Do you have two or more plug-ins with a /public/locale/en.yml/ file in 
each? If they have both have a brand: section, then one will override 
the other, even if only one defines a translation for the title: variable.


There has been a change between 2.8.1 and 3.1.1 in how plug-ins are loaded:


https://github.com/archivesspace/archivesspace/commit/1f4f34dd7cc655fc4a6e6d68cd8a5d8ff8c35cf8


Andrew.



On 30/03/2022 15:10, Nick Butler wrote:
> Hi all,
>
> We've been trying out ArchivesSpace v3.1.1 in development environments 
> prior to upgrading our production system from v2.8.1. We're 
> experiencing an issue whereby some of the entries in our local 
> plugin's |public/locales/en.yml|​ file seemingly aren't being 
> recognised. As far as I can tell, anything that's intended to override 
> an entry in the default file isn't being seen (i.e. the value of 
> |brand.title|​) , but everything new (i.e. entries in a |plugins|​ 
> block) is being loaded successfully. Using ArchivesSpace version 
> v2.8.1 again, without making any other changes, makes the locales load 
> as expected. All entries in the plugin's |frontend/locales/en.yml|​ 
> file are being respected as expected in both v2.8.1 and v3.1.1. Has 
> anyone else experienced this?
>
> Many thanks,
> Nick
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220331/3eb303ea/attachment.html>