UVE - Anchor links with internal IDs incorrectly handled as external routes in VTL pages

[KevinDavilaDotCMS]

Problem Statement

When opening a traditional VTL (Velocity Template Language) page within the UVE environment, anchor tags () containing href attributes referencing internal page IDs (e.g., #section-id) are being misinterpreted as external routes. Instead of scrolling to the target element, the system attempts to navigate and fetch a new page based on the ID. This results in a '404 Page not found' error, severely impacting user experience when interacting with common UI components like lists or tabs that rely on internal page referencing

2026-04-15.09-57-52.mov

Steps to Reproduce

1. Navigate to a traditional VTL-based page within the UVE environment.
2. Locate a UI element (such as a tab or list item) that uses an anchor tag with an ID reference (e.g., ).
3. Click on the anchor link.
4. Observe that the system attempts to perform a fetch/navigate action to a non-existent route.
5. Verify that a '404 Page not found' error message is displayed to the user.

Acceptance Criteria

The navigation logic must distinguish between internal ID fragments and external URL paths. Anchor links starting with '#' should trigger the default browser behavior for internal page scrolling/linking or be handled by the local component state (tabs/lists) without initiating a network fetch or a global route change. The '404 Page not found' error should no longer appear when clicking these links.

dotCMS Version

main a2f24da

Severity

Medium - Some functionality impacted

Links

https://dotcms.freshdesk.com/a/tickets/36261

[github-actions]

PRs linked to this issue

• feat(uve): Fix same-page navigation handling with anchors with id by @KevinDavilaDotCMS