"here" link on older record versions alert does not account for subpaths

[aseyedia]

Describe the bug

The "here" link in the alert that indicates that this item is not the latest version does not account for subpaths. Our PEDSpace instance is at pedsnet.org/metadata, but when we click on that link, we are redirected to pedsnet.org/entities/..., not pedsnet.org/metadata/entities/..., which, obviously, produces a 404.

You can clearly observe the issue on our public site here.

I've traced this issue to item-page-routing-paths.ts, though I'm not entirely sure if that's the root of the issue. Hopefully it's not a user error, but everything else about the site works as expected.

If I were to fix this on my own, I would find a way to pull in the subpath from the configuration file somehow and use that for the URI, though to be quite honest, again, I'm not entirely sure if this is the issue.

To Reproduce

1. Host a DSpace instance at a subpath (i.e. www.website.com/dspace)
2. Create an item.
3. Create a newer version of that item and enable showing all versions of items in search results.
4. Click on the "here" link where it says "This is not the latest version of this item. The latest version can be found here."

Expected behavior

What would be nice is if this link inserted the subpath before the base domain name e.g. website.com/dspace/item instead of website.com/item

[aseyedia]

Thinking about adding the frontend app configuration to get ui.namespace for the frontend.

import {
  APP_CONFIG,
  AppConfig,
} from '../../../../../config/app-config.interface';

[aseyedia]

Crudely adding it to item-page-routing-paths.ts like so did not yield expected results; instead, I was sent to /metadata/metadata/entities/...:

export function getEntityPageRoute(entityType: string, itemId: string) {
  if (isNotEmpty(entityType)) {
    const basePath = isProduction ? '/metadata/entities' : '/entities';
    return new URLCombiner(basePath, encodeURIComponent(entityType.toLowerCase()), itemId).toString();
  } else {
    return new URLCombiner(getItemModuleRoute(), itemId).toString();
  }
}

Trying to get the subpath from the ui's namespace variable also doesn't work; we get sent to /metadata/entities with no base URL for some reason:

import { Injector } from '@angular/core';
import {
  APP_CONFIG,
  AppConfig,
} from 'src/config/app-config.interface';
import { environment } from 'src/environments/environment';
...
export const isProduction = environment.production;
let appConfigValues: AppConfig;

export function getAppConfig(): AppConfig {
  return appConfigValues;
}

export function initAppConfig(injector: Injector) {
  try {
    appConfigValues = injector.get(APP_CONFIG);
  } catch (e) {
    console.error('Failed to get APP_CONFIG:', e);
  }
}

initAppConfig(Injector.create({
  providers: [
    { provide: APP_CONFIG, useValue: environment },
  ],
  parent: Injector.NULL,
}));
...
export function getEntityPageRoute(entityType: string, itemId: string) {
  if (isNotEmpty(entityType)) {
    const path = new URLCombiner(`${appConfigValues.ui.nameSpace}/entities`, encodeURIComponent(entityType.toLowerCase()), itemId).toString();
    console.log('Entity path:', path);
    return path;
  } else {
    return new URLCombiner(`${appConfigValues.ui.nameSpace}`, getItemModuleRoute(), itemId).toString();
  }
}

So clearly I'm doing something wrong but I don't know what. It still could also be user error.

[aseyedia]

If it helps, we've changed domain names more than once, and the subpath is new.