PUI footer links not working after upgrade to 4.2.0

[Scott Meyer-Kukan]

Hi all,

I've successfully upgraded to AS 4.2.0 from AS 4.1.1. Everything looks great with one exception, the footer links on the PUI are not working. I've attached a screenshot below. I thought this might be some type of error with the customizing we did a while back, but I cannot see where the edits are incorrect. Any thoughts on this? Everything else appears to be working perfectly.

Our PUI can be found at: https://archivesspace.erlibrary-archives.org/ 

Best,

Scott

[R. C. Miessler]

This seems to be an issue on a few 4.2 sites but I don’t see off-hand what they changed in the code that would cause this. Are you seeing the same thing in the staff interface?

 

Check your public/config/locales/en.yml file to make sure the footer section is populated for translations:

 

https://github.com/archivesspace/archivesspace/blob/9b6641ad34df5d1e8bf068465569642f63ffacce/public/config/locales/en.yml

 

You should see

 

  footer:

    staff_interface_html: <a href="%{staff_url}">Staff Interface</a>

    archivesspace_home_html: Visit <a href='http://archivesspace.org'>ArchivesSpace.org</a>

    feedback_html: <a id='aspaceFeedbackLink' href='%{feedback_url}' target='_blank'>Send Feedback or Report a Problem</a>

 

That’s all I can think of for now.

 

R.C. Miessler | Digital Initiatives Librarian, Special Collections and College Archives
Gettysburg College | Musselman Library

300 North Washington Street | Gettysburg, PA 17325

he/him/his

 

 

 

From: nonmemberar...@googlegroups.com <nonmemberar...@googlegroups.com> On Behalf Of Scott Meyer-Kukan
Sent: Monday, June 1, 2026 10:54 AM
To: Non-Member ArchivesSpace <nonmemberar...@googlegroups.com>
Subject: [non-member archivesspace] PUI footer links not working after upgrade to 4.2.0

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

---

--
You received this message because you are subscribed to the Google Groups "Non-Member ArchivesSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nonmemberarchives...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/nonmemberarchivesspace/c4109705-352e-4d0e-a332-6b090cd90a29n%40googlegroups.com.

[Scott Meyer-Kukan]

Hi,

Thanks for this information. 

I am not seeing the same thing on the staff side. The footer looks and works great on that end.

This may be a silly question, but where is the public/config/locales/en.yml file located? I am looking at archivesspace/plugins/local/public/locales/views/shared/_footer.html.erb file and that matches what you shared. But my unzipped version of AS 4.2 doesn't have a directory for public/config/locales/en.yml. Is that something that might be missing?

Best,

Scott

[R. C. Miessler]

The translation files for the PUI should be in \locales\public\

 

I just fired up a Docker container with 4.2, modified \locales\public\en.yml and it’s showing up as expected.

 

 

To view this discussion visit https://groups.google.com/d/msgid/nonmemberarchivesspace/345a9f6a-6c07-40b5-8183-4f89e7fddf80n%40googlegroups.com.

[Scott Meyer-Kukan]

Thanks! All of that matches what I have in the public/locales/en.yml file. The only modifications we've made are stored in the plugins/local/public/locales/en.yml file that is attached. I don't see what would be causing this in that file so I am not sure why this is happening here. 

Thanks for all your efforts on this.

Best,

Scott

[R. C. Miessler]

I just added your plugin en.yml file and it didn’t break anything,  so I’m guessing it’s something in your other customizations.

To view this discussion visit https://groups.google.com/d/msgid/nonmemberarchivesspace/e1c7da4b-7268-4dfe-a521-c47e01d184a6n%40googlegroups.com.

[Scott Meyer-Kukan]

Thank you for troubleshooting this with me! The culprit was a file in plugins/local/public/views/shared named _footer.html.erb. That was something created by a former hosting company back when we were running 3.5.1. Removing that file, which only contained information for the footer, has solved the issue. Everything looks great and appears to be fully functional.

Again, thanks for your help and support. Much appreciated.

Best,

Scott