PR-6.1-dev Pending

User tests: Successful: Unsuccessful:

avatar jiteshkhatri11
jiteshkhatri11
20 Apr 2026

Summary

Fixes an issue where publishing start and end date fields are not visible when creating a new article on the frontend.

Cause

The condition if (!is_null($this->item->id)) restricted the publishing fields to existing articles only, causing them to be hidden for new articles.

Fix

  • Removed the condition that restricted fields to existing articles
  • Ensured publish_up and publish_down are always displayed
  • Kept featured_up and featured_down fields restricted using permission check (access-change)

Testing Instructions

  1. Go to frontend article creation page
  2. Create a new article
  3. Verify that publishing start and end date fields are visible
  4. Edit an existing article and confirm fields still appear correctly

Expected result AFTER applying this Pull Request

  • Publishing start and end date fields are visible for both new and existing articles
  • Featured fields remain controlled by user permissions

Link to documentations

  • No documentation changes for guide.joomla.org needed
  • No documentation changes for manual.joomla.org needed

Checklist

  • I read the Generative AI policy and my contribution complies with it
avatar jiteshkhatri11 jiteshkhatri11 - open - 20 Apr 2026
avatar jiteshkhatri11 jiteshkhatri11 - change - 20 Apr 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 20 Apr 2026
Category Front End com_content
avatar jiteshkhatri11 jiteshkhatri11 - change - 20 Apr 2026
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2026-04-20 07:15:28
Closed_By jiteshkhatri11
Labels Added: PR-6.1-dev
avatar jiteshkhatri11 jiteshkhatri11 - close - 20 Apr 2026
avatar jiteshkhatri11
jiteshkhatri11 - comment - 21 Apr 2026

Hi @maintainers, I noticed this PR was closed.
I wanted to clarify if showing publishing dates for new articles is not intended behavior.

If there’s a preferred approach, I’d be happy to adjust the implementation accordingly.

Add a Comment

Login with GitHub to post a comment