dotCMS / dotCMS/core

[UVE]: Theme Selector Does Not Show Themes from Other Sites in Layout Editor

Open
#32,945 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : User Experience Priority : 3 Average stale Team : Scout Type : Defect
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

When editing a page in the Layout Editor (UVE), the Theme Selector does not show available themes from other sites. This blocks users from reusing shared styling assets across multi-site environments.

Steps to Reproduce
  1. Create a new blank site and add a new page.
  2. Open the page in the Layout Editor (UVE).
  3. Click on Layout > Theme.
  4. Observe that no themes are shown, even if other themes exist on different sites.
Expected Behavior
  • The Theme Selector should list themes available across all sites (unless explicitly restricted).
  • Editors should be able to apply cross-site themes when styling a page.
Acceptance Criteria
  • Themes from all sites are visible and selectable in the Theme Selector.
  • Theme application works correctly, regardless of where the theme is defined.
  • Any site-scoping rules are respected but clearly surfaced (e.g., labels, filters).
dotCMS Version

main / trunk

Proposed Objective

User Experience

Proposed Priority

Priority 2 – Important

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

Start by reproducing the issue in the UVE through Layout > Theme on a blank site, then trace how the Theme Selector loads themes and applies site-scoping rules. Done means themes from other sites are visible and selectable, application works across sites, and any restrictions are clearly surfaced.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.