dotCMS / dotCMS/core

FTM: Experiments - Homologate PageAPI response on Headless and Traditional

Open
#30,971 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue:

Within a variant, if we add content scheduled for future publication, the response in the contentlets array does not match the rendered attribute. This causes a discrepancy between Headless and Traditional content.

This issue is very similar to the one we resolved in: FTM: Homologate PageAPI responses on Headless and Traditional
We likely didn’t account for experiments in that fix.

Steps to reproduce:

  • Turn on Experiments, here are a little guide to goal this (The firsts paragraphs)
  • Create a variant from a page
  • Add to this variant a content that have a publishDate.
  • Start the experiment
  • Go to that variant in UVE, and select the LIVE view
  • Go to future day (to try to see the future content)

More explanation in the video.

https://github.com/user-attachments/assets/7c953da4-b845-4c10-b89c-27f956494714

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 reviewing the fix described in issue #31061, then follow the Experiments setup guide linked from issue #27565. Reproduce the variant scenario with future-dated content in UVE LIVE view, comparing the contentlets array with the rendered attribute while moving to a future day. Done means the PageAPI response matches the rendered content for both Headless and Traditional experiences when experiments are enabled.

Written by the indexing model from the issue text.

Assessment

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