fix(uve): add site URL option to copy URL popover in page editor

[gortiz-dotcms]

What does this PR do?

Adds a third Site URL entry to the copy URL popover in the UVE page editor. Previously, both the Live URL and Current View URL were always built from the admin login origin (or clientHost for headless pages), giving users no way to copy a link scoped to the currently selected site's public hostname.

The new entry appears only when site.hostname is set and it produces a URL that differs from the Live URL already shown, avoiding redundant entries.

Fixes

Closes #35448

Changes

• edit-ema-editor.component.ts — Extended $pageURLS computed to push a uve.toolbar.page.site.url entry when the site hostname differs from the current host.
• Language.properties — Added uve.toolbar.page.site.url=Site URL i18n key.
• edit-ema-editor.component.spec.ts — Added three new unit tests covering: site URL shown when hostname differs, suppressed when hostname matches clientHost, and suppressed when hostname is empty.

Test plan

• Open the page editor for a traditional (non-headless) page whose site hostname differs from the admin URL — the copy URL popover should now show a third "Site URL" entry pointing to https://<site-hostname>/<page-path>
• Open the page editor for a headless page where clientHost already matches the site hostname — only two URL entries should appear (no duplicate)
• Unit tests: yarn nx test portlets-edit-ema-portlet --testPathPattern=edit-ema-editor.component.spec

🤖 Generated with Claude Code

[claude]

Claude finished @gortiz-dotcms's task in 2m 36s —— View job

---

Review

• Read changed files
• Analyze logic and edge cases
• Check tests
• Post review

The change is small, focused, and well-tested. A few things worth a second look:

1. Hardcoded https:// ignores the actual scheme — and breaks port-bearing dev setups

edit-ema-editor.component.ts:1476

const siteHostUrl = new URL(path, `https://${site.hostname}`).toString();

Recent commit 6bfb3e41 deliberately hardcoded the scheme. A few consequences:

• A dotCMS instance accessed over http://demo.dotcms.com produces liveUrl = http://... and siteUrl = https://... — they will not dedupe and the popover will show two near-identical entries. Users who copy "Site URL" land on a non-existent HTTPS endpoint.
• For dev environments running on http://localhost:8080, the site URL will be https://localhost/... which is unreachable. A copy-button that gives an invalid URL is worse than no button.
• If the site is on a non-standard HTTPS port (e.g. :8443) and the hostname isn't stored with the port, the URL is wrong.

Worth either: (a) using the live URL's protocol/port, (b) preferring site.httpsRequired-style flag if one exists, or (c) explicitly documenting that this is an intentional production-only assumption.

2. Silent catch {} makes malformed-hostname diagnostics invisible

edit-ema-editor.component.ts:1484

catch {} swallows everything. If a site is misconfigured (whitespace in hostname, non-ASCII without IDN encoding, etc.), the Site URL just silently disappears with no clue why. A one-line console.warn (or the project's logger) would help support debug this when it shows up in the field. Not blocking.

3. Dedup only checks liveUrl, not currentViewUrl

The condition is siteHostUrl !== liveUrl. The current view URL is built via createFullURL(...) which uses clientHost || window.location.origin — it can also coincide with the site hostname (e.g. when there are no extra params). In practice it almost always carries language_id/persona params so this is unlikely, but it means duplicates can theoretically appear when currentViewUrl happens to be hostname-only. Probably fine; flagging because the dedup invariant is "show only when distinct" and the check is partial.

4. The "case-insensitive dedup" test passes by luck of URL normalization

edit-ema-editor.component.spec.ts:993-1019

Earlier commit 69d2d902 dropped the explicit toLowerCase() because URL lowercases the host automatically. That's correct — but the test name implies the code does case-insensitive dedup explicitly. Worth a comment in the code (or test) noting the dedup correctness depends on URL normalization, not on a comparator. Future refactors could regress this.

5. Malformed-hostname test relies on URL throwing for spaces

edit-ema-editor.component.spec.ts:965-991

new URL('/path', 'https://invalid host name') throws in Node/V8 today, but URL parser leniency varies across engines. If a test runner upgrade ever changes this, the test would silently start asserting a different code path (URL construction succeeds, dedup-by-equality kicks in instead of the catch). Low priority but brittle.

6. Minor: comment-free try/catch masks intent

A short // hostname may be malformed; skip site URL if URL ctor throws would document why the catch is empty rather than relying on the test name.

---

Tests cover the meaningful branches (hostname differs, matches, system-host, empty, port mismatch, casing, malformed). Good coverage.

The biggest risk is #1 — hardcoded https:// is a real footgun in non-prod and HTTP-only deployments. Worth confirming this is the desired UX before merging.
• Branch

[gortiz-dotcms]

Closing because PR 35539 already solved the issue

https://github.com/dotCMS/core/pull/35539/changes#diff-24dc496db1eb6feb3e10a031baa4b4b63c20f1cd02ade574065f6b967f11c365R1615-R1636

core-web/libs/portlets/edit-ema/portlet/src/lib/edit-ema-editor/edit-ema-editor.component.ts
lines 1615-1636