dotCMS / dotCMS/core

[Edit Content]: Cannot Access Templates from Other Sites When Creating a Page

Open
#32,944 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Problem Statement

When creating a page under a new site, users are unable to access templates from other sites. The Template Selector is incorrectly scoped, preventing shared or global templates from being reused.

Steps to Reproduce
  1. Create a new blank site.
  2. Attempt to create a new page within that site.
  3. Open the Template Selector.
  4. Notice that only templates specific to the current site (or none at all) are available.
Video

https://github.com/user-attachments/assets/b9b8650e-0750-49d7-a6d0-154ab115f297

Expected Behavior
  • The Template Selector should display templates available across all sites, not just the current one.
  • Users should be able to reuse templates from existing sites when creating pages in new or alternate sites.
Acceptance Criteria
  • The Template Selector allows selecting templates from all available sites.
  • UI and filtering logic reflect proper permissions and access rules.
  • No regressions when working in site-scoped template contexts.
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 blank-site flow described in the issue and inspect the Template Selector entry point and its site-scoped filtering and permission checks. Done means templates from permitted sites can be selected for a new page, while existing site-scoped behavior remains unchanged and the relevant regression coverage passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
content, 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.