Closed (duplicate)
Project:
Drupal core
Version:
10.1.x-dev
Component:
datetime.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Feb 2006 at 12:54 UTC
Updated:
22 Oct 2022 at 21:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
sammys commented+1
Bumping this up as it's easy to patch in and test.
Comment #2
Crell commentedThis now belongs to CVS.
I like the concept, and worked for me perfectly when I tested it on the daily module. I don't see any bugs, and it's a nice feature to have. +1.
Comment #3
drummI think the best place for this would better be implemented as a defualt value in system_elements().
Comment #4
catchComment #5
Jaza commentedThe respective start and end years '1900' and '2050' are still hard-coded into expand_date(). Ergo, this patch is still needed. Bumping.
Comment #6
valthebaldThat looks like useful feature, and good for novices too
Comment #7
xjmActually, given how far it is past the feature and API freeze deadlines, this is for 9.x at this point (or maybe a minor version of 8.x, but in that case we can move it back after 8.0 is released). This issue might not even be relevant anymore and the original patch is certainly not useful. :)
Comment #8
catchComment #19
quietone commentedI don't see any reason for this to be postponed and datetime.module seems a better fit (I hope).
Comment #20
aritrika.d commentedComment #22
vikashsoni commentedPatch not working giving error while applying in drupal-9.3.x-dev
Comment #23
quietone commented@vikashsoni thank you for looking into this issue but there is never a need to show screenshots of patch applications. If you discover a patch does not apply it is best to leave a comment explaining what you did and what version of Drupal you were testing with. And then if a reroll is needed add the tag, 'Needs reroll'. Therefor, credit has been removed per How is credit granted for Drupal core issues.
Comment #27
jaime@gingerrobot.com commentedComment #28
jaime@gingerrobot.com commentedThis feature should be covered by https://www.drupal.org/project/drupal/issues/2840220