dotCMS / dotCMS/core

Content Type under one site showing up in other sites

Open
#31,385 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Parent Issue

No response

Problem Statement

See attached screen grab.

When creating a content type under a specific site, the content type shows up in other sites. Users can use that content type in the other sites to create a piece of content, but that content does not show up in the site, it shows up in the site the content type has been created under. This is confusing to end users.

If a content type is created under a specific site, it should only be available to that site.

Steps to Reproduce

Please see video

  1. Make sure instance has at least two sites
  2. Create content type and set the site/folder field for the content type to one specific site
  3. Use the site picker to change the site to a site that is NOT the site the content type has been created under
  4. Create a piece of content using the new content type
  5. You will not see the new piece of content in that site
  6. Navigate to the site the content type was created under
  7. You will be able to see the content created in the other site
Acceptance Criteria

When a content type is created under a site, it should only be available to that site, you should not be able to view it or create content from it in other sites

dotCMS Version

25.01.30
demopm instanace

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

EJ Americas customer brought this issue up in a call. I replicated it on our demopm instance. It is not a showstopper but it is causes confusion and degrades the perception of our application.

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

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 with two sites, a site-specific content type, the site picker, and a created content item. Trace how the content type's site/folder selection affects availability across sites. Done means the type cannot be viewed or used to create content from any other site, while remaining available in its own site.

Written by the indexing model from the issue text.

Assessment

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