[Archivesspace_Users_Group] PUI locales not being fully loaded in v3.1.1?
npwb2 at cam.ac.uk
Thu Mar 31 04:55:17 EDT 2022
Thanks for your reply. That doesn't appear to be the case here (either in my dockerised local development environment, where this is my only active plugin, or in our development server, where there are no other public/locale/* files in any of our other currently-loaded plugins). Thanks for pointing that commit out, it looks like the related PR (https://github.com/archivesspace/archivesspace/pull/2266) made a number of other changes to plugins as well. I'll take a closer look.
Hm plugin enhancements from #1896 by lorawoodford · Pull Request #2266 · archivesspace/archivesspace<https://github.com/archivesspace/archivesspace/pull/2266>
Includes 30 commits from the larger #1896 written by @marktriggs @jambun @payten and funded by Queensland State Archives. 3dc860a: Introduce AbstractPluginSection (and examples) to allow arbitrar...
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk>
Sent: 31 March 2022 08:54
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] PUI locales not being fully loaded in v3.1.1?
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:
On 30/03/2022 15:10, Nick Butler wrote:
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?
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group