postponed on #216961: Make author/submitted by separate toggles
and related to comments #70-#74 on #143434: Usability Issue: Post Information Settings

Allow a (drop down) configuration option to pick the format of the date displayed for the publication date.
in D6, admin/settings/date-time/formats, Admin -> Site Configureation -> Date and Time
has a setting allowing the creation of new Date formats. It would be cool to make a "Book Year" format, and on content types for Book, be able to pick that format for displaying the publication date in the post settings.

So for each content type:

Display Settings:
[ ] Display authors username
[ ] Display creation date
--- Select date format: [drop down: long, short, etc. ] (?)

The Select could be disabled or grayed out if the display date is unchecked.

And the (?) help would open up a link to the Admin Date and Time settings page and include a statement like: Change current date and time formats or create a new format.

CommentFileSizeAuthor
#15 477170-13-content_type_date_format.patch138.9 KBmadhavvyas
#13 477170-11-content_type_date_format.patch48.56 KBmadhavvyas
#11 477170-11-content_type_date_format.patch48.67 KBmadhavvyas
#9 477170-5-content_type_date_format-2.patch66.24 KBMiguel.kode
#5 477170-5-content_type_date_format.patch2.48 KBadammalone

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Issue tags: +Needs usability review

Hm. At first glance, I think this is overkill, and something that'd be easy enough to add in with a contrib module if you want to give people that much control.

Tagging for other opinions.

sun.core’s picture

sun.core commented
Version: 7.x-dev » 8.x-dev
Bojhan’s picture

Bojhan commented
Issue tags: -Needs usability review

Yhea, no this is a bad idea. Look at Joomla, they have accepted all these kind of feature requests.. You can easily edit this in the theming.

wickwood’s picture

wickwood commented

Just to add my 2¢...

It may be easy to edit the post date in the theme and I'm going to find out shortly because I'm in need of changing the format of the post dates for the site I'm working on. But just to let you know, I've spent hours now trying figure where to make this change.

What I don't understand is why it's not something that is configurable form the admin area?
Why should we be able to set up different time formats, indeed as many as we want, but we are not be able to use them for something as simple as the post date?

Having to go dig into the code of the theme for this seems a little silly to me?

Steve

adammalone’s picture

adammalone
Primary language English
Location San Francisco
commented
Status: Postponed » Needs review
StatusFileSize
new 477170-5-content_type_date_format.patch2.48 KB

I made a patch for D8 where the user may change the date format per content type. I think this is the most relevant issue to attach this to.

It arose due to the desire on a D7 site to have some formats for some content types and others for others. Assumed there had to be an option in the admin interface but found there was none and had to override in preprocess.

I think the key thing to remember here is, although it may be easy for a developer to override any date/time format; a user who just wants a simple blog or ecommerce website doesn't really have the option to specify post date format (unless I'm missing something)

alansaviolobo queued 5: 477170-5-content_type_date_format.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 5: 477170-5-content_type_date_format.patch, failed testing.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Version: 8.0.x-dev » 8.1.x-dev
Issue summary: View changes
Issue tags: +Needs reroll

This likely could still be done in 8.1.x

Miguel.kode’s picture

Miguel.kode commented
Status: Needs work » Needs review
StatusFileSize
new 477170-5-content_type_date_format-2.patch66.24 KB

This is the re-roll for this patch. I changed:

- core/modules/node/content_types.js
- core/modules/node/node.module

I removed: core/modules/node/content_types.inc

Status: Needs review » Needs work

The last submitted patch, 9: 477170-5-content_type_date_format-2.patch, failed testing.

madhavvyas’s picture

madhavvyas commented
Status: Needs work » Needs review
Issue tags: -Needs reroll
StatusFileSize
new 477170-11-content_type_date_format.patch48.67 KB

Patch re rolled

Status: Needs review » Needs work

The last submitted patch, 11: 477170-11-content_type_date_format.patch, failed testing.

madhavvyas’s picture

madhavvyas commented
Status: Needs work » Needs review
StatusFileSize
new 477170-11-content_type_date_format.patch48.56 KB

Updated patch

Status: Needs review » Needs work

The last submitted patch, 13: 477170-11-content_type_date_format.patch, failed testing.

madhavvyas’s picture

madhavvyas commented
StatusFileSize
new 477170-13-content_type_date_format.patch138.9 KB

By mistake I re-rolled with 8.0.x It is corrected

madhavvyas’s picture

madhavvyas commented
Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 15: 477170-13-content_type_date_format.patch, failed testing.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Needs work » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

smustgrave’s picture

smustgrave commented

wanted to bump this feature 1 more time.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.