craftcms / craftcms/cms

[5.x]: Field postDate and expiryDate can't be made visible for entries

Open
#13,954 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

What happened?
Description

Not sure if this is supposed to be a bug or a feature request.

In CraftCMS 5 entry types are stored in the entries table.
Therefore they also have the fields postDate and expiryDate.

By manually setting an old date to an entry via the database it disappears from the frontend output.
Therefore the logic is already implemented.

But there is no way to make the fields visible in the backend expect by creating a section for it.
Also by opening the entry with the edit view, the fields are not shown.
image

Solutions

the fields should be visible globally or optionally at an entry level with a toggle.
This could be also added to the dropdown menu for matrix table
ex:
image

Benefit

Entries can in addition of being disabled, also be scheduled or hidden in the future identical to sections.

Craft CMS version

5

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

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

The issue names no files, tests, or entry points. Start by clarifying whether postDate and expiryDate should be globally visible or configurable per entry, then define the expected editing and scheduling behavior; done should cover an agreed backend UI and frontend visibility behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.