dotCMS / dotCMS/core

[DEFECT] UVE Experiments: "Not Configured" Error Displayed After Browser Reload

Open
#34,349 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Team : Scout
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

There is a state persistence issue within the Universal Visual Editor (UVE) when interacting with the Experiments portlet. When a user is actively viewing or editing experiments on a page and performs a manual browser reload, the portlet fails to re-initialize the existing configuration. Instead, it displays an error message stating that "Experiments is not configured," even if the configuration was active and visible prior to the refresh.

Steps to Reproduce
  1. Open the UVE and navigate to a page in Edit Mode.
  2. Click on the Experiments icon/tab in the sidebar to open the portlet.
  3. Ensure an experiment is active or the configuration is visible.
  4. Perform a manual browser reload (F5 or Cmd+R) while the Experiments portlet is open.
  5. Observe: After the page reloads, the Experiments portlet displays a "not configured" state or error message.
Video

https://github.com/user-attachments/assets/4483517a-e2e3-4e06-9584-18176ac2a62f

Acceptance Criteria
  • The Experiments portlet must correctly persist or re-fetch its configuration state following a browser reload.
  • Users should be returned to the active experiment view they were on prior to the refresh without seeing a "not configured" error.
  • Verify that the UVE initialization sequence correctly loads experiment context during the boot process.
dotCMS Version

main/trunk/evergeen

Severity

Medium - Some functionality impacted

Links

NA

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure by opening the UVE Experiments portlet in Edit Mode with an active configuration, then performing a browser reload. Trace the UVE initialization sequence and the Experiments portlet's configuration loading; done means the existing experiment view is restored without the "not configured" error.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.