WordPress.org

Make WordPress Core

Opened 6 years ago

Last modified 6 months ago

#26980 reopened defect (bug)

the_modified_date is lower than the_date when post is scheduled

Reported by: tushonline Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 3.8
Component: Date/Time Keywords: needs-patch
Focuses: Cc:

Description

I scheduled a post on 30th Jan for 1st Feb. When the post was published, the modified date shows lower than the published date.

I am using <?php the_date('F j, Y'); ?> for first part & <?php the_modified_date('F j, Y'); ?> for the second part.

https://dl.dropboxusercontent.com/u/1830109/wp-381-date.jpg

This should show the_modified_date = the_date in case of scheduled posts?

Thoughts?

Change History (6)

#1 follow-up: @knutsp
6 years ago

  • Keywords close added

I have no problem accepting that a post is modified before it's published. The automated publishing itself is not a modification. Only humans should be able modify.

#2 follow-up: @wonderboymusic
4 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Thanks for the report, @tushonline. Closing this since there's been no activity in 20 months. I agree with @knutsp's remarks in comment:1

#3 in reply to: ↑ 2 @tushonline
4 years ago

Thanks for the update. Best wishes. Keep up the great work. ♥ WordPress.

#4 in reply to: ↑ 1 @uatania
9 months ago

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Replying to knutsp:

I have no problem accepting that a post is modified before it's published. The automated publishing itself is not a modification. Only humans should be able modify.

I disagree because the modified date often it's used as data in some feeds and sitemaps where this can be treated as an error.

(Sorry for reopening the discussion a lot of years later.)

#5 @Rarst
6 months ago

  • Keywords needs-patch added; close removed

I think that discrepancy between "human" and code modification of post instance can be very confusing in this and other instances.

Tentatively my opinion is that we should aim to "any change is a change" handling of it to maximize consistency.

#6 @SergeyBiryukov
6 months ago

  • Milestone set to Awaiting Review
Note: See TracTickets for help on using tickets.