Content being published automatically without publish action

[mboutillette-dotcms]

Parent Issue

Problem Statement

Have noticed this behavior on several environments including demo, demopm, dotcms.com.
When a content type has scheduled publishing set up, all content is published right away no matter what date is put in the field and without actually putting the piece of content through Publish workflow step.

See the video recording for what happens on the Demo instance

Steps to Reproduce

Steps to reproduce:

1. Ensure content type has a date/time field and that field is selected as the Publish Date Field (as it is for blogs on the demo.dotcms site)
2. Ensure that there is at least a one step workflow with Save in it (there does not even need to be publish)
3. Create a piece of content of that type and set the date to publish as a future date
4. Save the piece of content
5. Within a few seconds the piece of content shows up on the site, though the status indicator remains as unpublished in the backend.

Acceptance Criteria

When using scheduled publishing the content should not be published until the date selected AND it should not be published unless a user has explicitly taken the Publish action.

dotCMS Version

25.01.30

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

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

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[fabrizzio-dotCMS]

Perhaps the publish date field isn't selected on the Edit content screen.

This is a crucial step for the scheduled publishing to work correctly

[mboutillette-dotcms]

Actually, testing this further and it may not have to do with schedule publish. Even on content types with no schedule publish date, the content is being published. Check out demopm right now, create a new product and just save it (don't publish it). It will show up on the live site.

[mboutillette-dotcms]

Thanks Fabrizzio for going through this with me. So it looks like a user will need to use incognito window to view the site if they have been logged into the back end in the same browser session. I'll look back at the other issue that is on dotcms.com and see if I can post an example of that, but we are working with Ivan on that now as well.