Refresh does not take from i18n/en.json

[ardprasad]

Describe the bug

I am trying to add a few more items to footer. For example, "Credits". I created the required files under src/app/info/credits/credits-content/credits-content.component.html etc.
I created credits.info.credits.head entry in en.json5 file to display "Contributors"
I open in browser, it show perfectly, but I refresh, it show 'info.credits.head' instead of 'Contributors'.
More surprisingly, the footer shows footer.link.privacy-policy NOT "Privacy Policy"

To Reproduce

Steps to reproduce the behavior:

1. Do this: http://localhost:4000 (Shows correctly)
2. If I refresh the page: en.json5 is not effect

Expected behavior

A clear and concise description of what you expected to happen.

Related work

Link to any related tickets or PRs here.

[alanorth]

Hi @ardprasad. We will need more information before we can be sure this is a bug. It sounds like you are using a custom component, as src/app/info/credits/credits-content/credits-content.component.html does not exist in DSpace. Can you try reproducing this with a built-in DSpace component and updating the issue with steps to reproduce? Thanks!

[tdonohue]

Also @ardprasad , what version of DSpace are you using? We need more information to understand what may be going on.

[ardprasad]

HI, Thank you for your response. Here is my problem statement. ------- I work on Linux Mint 22.01 OS and Dspace-9-Rc1. I am preparing a LiveDVD/USB using Cubic. I host the .iso file on sourceforge. Installed openjdk-17-jdk postgresql git vim maven ant curl tomcat10 environment is: export PATH=$PATH:/usr/lib/jvm/java-17-openjdk-amd64/bin export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64/ export CATALINA_HOME=/usr/share/tomcat10 export CATALINA_BASE=/var/lib/tomcat10 export CATALINA_TMPDIR=/tmp export JAVA_OPTS=-Djava.awt.headless=true export NODE_OPTIONS="--max-old-space-size=8192"

…

-------- I cleared firefox browser cache. npm cache clear –force npm run build:prod

-------- I created About, Credits, Invitation to submit, Help in the footer

------------ Then I run the following commands to test and access DSpace using http://localhost:4000 It works impeccably. But when I refresh any page, the DSpace does not use en.json5, and show the system internal reference like the following menu.section.browse_global_communities_and_collections menu.section.browse_global menu.section.statistics Attached are the screenshot before and after refresh in firefox browser with best regards -- ARD Prasad, Ph.D., Former Professor & Head, Documentation Research and Training Centre (DRTC) Indian Statistical Institute Mobile: +91 944 902 6528

On Mon, 14 Apr 2025 at 19:37, Alan Orth ***@***.***> wrote: Hi @ardprasad <https://github.com/ardprasad>. We will need more information before we can be sure this is a bug. It sounds like you are using a custom component, as src/app/info/credits/credits-content/credits-content.component.html does not exist in DSpace. Can you try reproducing this with a built-in DSpace component and updating the issue with steps to reproduce? Thanks! — Reply to this email directly, view it on GitHub <#4181 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALNBA7ISFK3DW5ZTMWOXDQT2ZO6JNAVCNFSM6AAAAAB3BY7BC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBRHAZTMMRWHE> . You are receiving this because you were mentioned.Message ID: ***@***.***> *alanorth* left a comment (DSpace/dspace-angular#4181) <#4181 (comment)> Hi @ardprasad <https://github.com/ardprasad>. We will need more information before we can be sure this is a bug. It sounds like you are using a custom component, as src/app/info/credits/credits-content/credits-content.component.html does not exist in DSpace. Can you try reproducing this with a built-in DSpace component and updating the issue with steps to reproduce? Thanks! — Reply to this email directly, view it on GitHub <#4181 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALNBA7ISFK3DW5ZTMWOXDQT2ZO6JNAVCNFSM6AAAAAB3BY7BC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBRHAZTMMRWHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tdonohue]

@ardprasad : I'm not able to reproduce the problem you've detailed in your last comment. If I run the latest code (on main branch) as of today, then it builds fine using npm run build:prod. I can then run it in production mode using npm run serve:ssr. When I access it from my browser, the site works properly. If I reload the page, the i18n keys still load English.

It is possible that a recent change fixed whatever side effect you were seeing. But, I cannot reproduce this issue as of today.

I'd recommend updating to the latest main code, and trying again. If you can find a way to reproduce this still, I think we'd need more information. For now, I'm flagging this as "cannot reproduce"

[ardprasad]

Hi, Thank you for your reply. If I default footers everything goes on well, while I was creating LiveCD of dspace-9.0-rc1. When I add my footer and try npm run start:dev, the extra menu item (e.g: credits ) work perfectly even when I refresh it browser. But when I try: npm run server:ssr or npm run build:prod, things go completely wrong. Even the regular menu appear as below: menu.section.browse_global_communities_and_collections <http://localhost:4000/community-list> menu.section.browse_global menu.section.statistics <http://localhost:4000/statistics> I am attaching the tarball file of src I will try the latest main and report it back to you with best regards -- ARD Prasad, Ph.D., Former Professor & Head, Documentation Research and Training Centre (DRTC) Indian Statistical Institute Mobile: +91 944 902 6528

…

On Wed, 23 Apr 2025 at 21:34, Tim Donohue ***@***.***> wrote: *tdonohue* left a comment (DSpace/dspace-angular#4181) <#4181 (comment)> @ardprasad <https://github.com/ardprasad> : I'm not able to reproduce the problem you've detailed in your last comment. If I run the latest code (on main branch) as of today, then it builds fine using npm run build:prod. I can then run it in production mode using npm run serve:ssr. When I access it from my browser, the site works properly. If I reload the page, the i18n keys still load English. It *is* possible that a recent change fixed whatever side effect you were seeing. But, I cannot reproduce this issue as of today. I'd recommend updating to the latest main code, and trying again. If you can find a way to reproduce this still, I think we'd need more information. For now, I'm flagging this as "cannot reproduce" — Reply to this email directly, view it on GitHub <#4181 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALNBA7OWP72CGKZDB5EDYHT2262ZFAVCNFSM6AAAAAB3BY7BC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRUHAYDMMRWGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ardprasad]

Hi, unfortunately, I could not attach src.tar.gz. Following are the files I created and modified to have 4 more items in the footer app/info (about, credits, enduseragrement, feedback, help, invite, privacy) themes/custom/app/info (about, credits, enduseragrement, feedback, help, invite, privacy) app/info/info-routes.ts app/info/info-routing-paths.ts app/footer/footer.component.html app/footer/footer.component.spec.ts app/footer/footer.component.ts assets/config.json assets/i18n/en.json5 config/default-app-config.ts config/info-config.interface.ts environments/environment.test.ts themes/custom/lazy-theme.module.ts with best regards -- ARD Prasad, Ph.D., Former Professor & Head, Documentation Research and Training Centre (DRTC) Indian Statistical Institute Mobile: +91 944 902 6528

…

On Wed, 23 Apr 2025 at 23:29, Prasad Ard ***@***.***> wrote: Hi, Thank you for your reply. If I default footers everything goes on well, while I was creating LiveCD of dspace-9.0-rc1. When I add my footer and try npm run start:dev, the extra menu item (e.g: credits ) work perfectly even when I refresh it browser. But when I try: npm run server:ssr or npm run build:prod, things go completely wrong. Even the regular menu appear as below: menu.section.browse_global_communities_and_collections <http://localhost:4000/community-list> menu.section.browse_global menu.section.statistics <http://localhost:4000/statistics> I am attaching the tarball file of src I will try the latest main and report it back to you with best regards -- ARD Prasad, Ph.D., Former Professor & Head, Documentation Research and Training Centre (DRTC) Indian Statistical Institute Mobile: +91 944 902 6528 On Wed, 23 Apr 2025 at 21:34, Tim Donohue ***@***.***> wrote: > *tdonohue* left a comment (DSpace/dspace-angular#4181) > <#4181 (comment)> > > @ardprasad <https://github.com/ardprasad> : I'm not able to reproduce > the problem you've detailed in your last comment. If I run the latest code > (on main branch) as of today, then it builds fine using npm run > build:prod. I can then run it in production mode using npm run serve:ssr. > When I access it from my browser, the site works properly. If I reload the > page, the i18n keys still load English. > > It *is* possible that a recent change fixed whatever side effect you > were seeing. But, I cannot reproduce this issue as of today. > > I'd recommend updating to the latest main code, and trying again. If you > can find a way to reproduce this still, I think we'd need more information. > For now, I'm flagging this as "cannot reproduce" > > — > Reply to this email directly, view it on GitHub > <#4181 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ALNBA7OWP72CGKZDB5EDYHT2262ZFAVCNFSM6AAAAAB3BY7BC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRUHAYDMMRWGY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[tdonohue]

Hi @ardprasad : I'm sorry, but this mode of communication isn't working. We are not getting any attachments or images when you email in response to this ticket. From what you've said, my best guess is your issues are related to customizations you've made. You may want to try temporarily reverting those customizations to see if it allows DSpace to behave properly. If so, then you could add in the customizations little by little to see where it breaks.

If you require additional support, I'd recommend using one of the support options listed at https://wiki.lyrasis.org/display/DSPACE/Support There are mailing lists listed there which may work better for you, if you would rather communicate via email.

For now, I'm going to close this ticket as "not reproducible". If we discover later that this is a bug in DSpace, we can always reopen the ticket as necessary.