Hi guys,

Thanks for an awesome CCK module. Just one thing i found wrong with it and i think its a bug.

I am the module to display a CCK date field on a node. It only allows to input the year and shows -70years and + 3years according to the date.
However when the user selects a year on a node, submits it and then goes back to edit it, the year selection shows - 70 years from the previously chosen date. And so it seems to show values relative to the chosen date and not todays date. The user cannot change the date.

I believe it should still show -70 years from todays date.

Anyway of doing this?

Thanks!

waffle182

Comments

KarenS’s picture

KarenS CreditAttribution: KarenS commented
Status: Active » Closed (works as designed)

That's by design to be sure the chosen date never drops out of the available range. This is changed in the 5.2 version so it centers on the current date and extends backwards as far as it needs to to pick up the date's year.

bleen’s picture

bleen CreditAttribution: bleen commented
Version: 5.x-1.8 » 6.x-2.6
Status: Closed (works as designed) » Active

I'm still seeing this behavior in 6.x-2.x Is that still "as designed?"

vince.rowe’s picture

vince.rowe CreditAttribution: vince.rowe commented

Hi there,

We are still seeing this in 6.x-2.7

As it kicks in using the JQuery popup as well, it means if a user selects the wrong date they can never select the correct one.

Example:

Date range set to -30:0
So 30 years back, 0 years forward.

If you want 1991 but select 1990 by mistake, you can now only see 1990 - 1960. So a user can never select what they want unless they hit refresh.

If the node is saved, then its impossible to fix the error without deleting the node and creating it again.

Vince

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Component: Date CCK Field » Code
Issue summary: View changes
Status: Active » Closed (won't fix)

Unfortunately the Drupal 6 version of the Date module is no longer supported. That said, we appreciate that you took time to work on this issue. Should this request still be relevant for Drupal 7 please feel free to reopen it. Thank you.