Client side rendering (CSR) ignores nameSpace configuration causing broken resource loading

[milanmajchrak]

References

• Fixes CSR ignores namespace configuration causing broken resource loading #4637

Description

Fix CSR ignoring namespace configuration, causing broken resource loading when DSpace is deployed with a custom namespace (e.g., /repository).

Instructions for Reviewers

List of changes in this PR:

1. Modified clientSideRender() function to dynamically replace base href with namespace configuration
2. Added REST URL replacement logic to CSR for consistency with SSR behavior

How to test:

1. Configure DSpace with ui.nameSpace: /repository
2. Exclude SSR for the ^/search$" page
3. Go to the /repository/search and refresh the page

Expected behaviour:

• The search page has loaded correctly; you are not seeing a blank page

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[bkeese]

+1 This fixes the same problem in our 7.6.5 instances.

[tdonohue]

👍 Thanks @milanmajchrak ! I was able to verify the bug also exists on main, and was able to verify this PR fixes the issues.

Merging this into 7.x and auto-porting to all other active branches.

[dspace-bot]

Successfully created backport PR for main:

• [Port main] Client side rendering (CSR) ignores nameSpace configuration causing broken resource loading #4772

[dspace-bot]

Successfully created backport PR for dspace-8_x:

• [Port dspace-8_x] Client side rendering (CSR) ignores nameSpace configuration causing broken resource loading #4773

[dspace-bot]

Successfully created backport PR for dspace-9_x:

• [Port dspace-9_x] Client side rendering (CSR) ignores nameSpace configuration causing broken resource loading #4774