[DEFECT] UVE detection mechanism fails causing incorrect analytics activation

[oidacra]

Problem Statement

When a page is viewed within the Universal Visual Editor (UVE), the detection mechanism that identifies whether the page is running inside UVE is not working correctly. This causes analytics to activate incorrectly when it should be disabled inside the UVE context. This impacts content editors working within UVE, causing unwanted analytics tracking during content editing sessions.

Technology: Front-end (UVE detection mechanism)

Steps to Reproduce

Detailed steps:

1. Open a page within the Universal Visual Editor (UVE)
2. Observe that analytics is being activated during the editing session
3. Verify that the UVE detection mechanism (the system that tells if content is being viewed inside UVE) is not working properly
4. Confirm analytics events are being fired when they should be suppressed inside UVE

Acceptance Criteria

• UVE detection mechanism correctly identifies when a page is being viewed inside UVE
• Analytics is disabled/suppressed when content is viewed within UVE context
• Analytics only activates for pages viewed outside of UVE (normal page views)
• Verify no analytics events are fired during UVE editing sessions
• Existing analytics functionality remains unchanged for normal page views

dotCMS Version

Latest from main branch

Severity

Medium - Some functionality impacted

Links

NA

[github-actions]

PRs linked to this issue

• feat(analytics): disable all tracking inside UVE editor by @oidacra