Also, after I save the node, the date chosen is listed as today's date and not the date chosen in the popup.

Thanks.

Comments

aaronelborg’s picture

aaronelborg commented

Actually, I'm willing to bet it has something to do with my custom date format:

l, F jS, g:i a

Is that^^ no good?

Seems to be fine in other contexts.

mikeytown2’s picture

mikeytown2 commented

On admin/content/node-type/*/fields/field_date under
Input format: Set the order and format for the date parts in the input form. The format will be adapted to remove values not in the granularity for this field.
Custom input format: The custom format, if provided, will override the input format selected above. The custom format, if provided, will override the selected display or input options. Define a php date format string like 'm-d-Y H:i' (see http://php.net/date for more details).

Custom input format is broken it seems.

aaronelborg’s picture

aaronelborg commented

l, F j, g:i a

Doesn't work for me either.

This gives todays date after saving the node.

Bottom line: custom date field doesn't seem to work.

mikeytown2’s picture

mikeytown2 commented
Title: After choosing a date from popup, the date field is populated with an appended "S" » Custom input format in admin/content/node-type/*/fields/field_* broken. Choose date from popup, always set to now.
mikeytown2’s picture

mikeytown2 commented

If you where to run the unix time stamp through the date function then the date would be valid... right?

ChrisRut’s picture

ChrisRut commented

:subscribing:

karens’s picture

karens commented
Status: Active » Postponed (maintainer needs more info)

Could someone please provide a detailed summary of how to reproduce the problem on a fresh site? What kind of date field are you creating? What widget are you using? What settings did you choose? What format did you try to set up?

Make sure you get a reproducable result on a fresh install with nothing else installed to be sure the problem is not some reaction with other modules.

karens’s picture

karens commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

No response, closing.

ericxb’s picture

ericxb commented

hm... On version 7.x-1.0-alpha2, I can report a similar problem.

New drupal 7 site. Created custom content type with 2 date fields. One has a custom display format of "l, F j Y" (i.e. granularity of year, month, day). And the input format is one of the defaults: "03/04/2011 - 22:19:09". It works OK.

The second has a custom display of "g:i a" and the same string as the input format. The granularity is set to "year, hour, minute". Obviously the year granularity is included only because it's required. Providing input like "8:00 am" returns the error: "Start Time From date value #1 is invalid." (presumably, "value" is a zero based count)

If that doesn't provide enough context, I'm happy to provide an admin account; or dump some variables.

mac_weber’s picture

mac_weber commented
Version: 6.x-2.4 » 7.x-2.x-dev
Priority: Normal » Major
Status: Closed (won't fix) » Active

Same problem here as
#9 ericxb described. It is impossible to use custom input. I'm trying to get input of "G:i". Even if I include year on the input format it does not work.

mac_weber’s picture

mac_weber commented
Component: Date Popup » Date CCK Field

related to the field, not just pop-up

Anonymous’s picture

Anonymous (not verified) commented
Version: 7.x-2.x-dev » 7.x-2.0-alpha3

I am having the same issue. There does not seem to be a way to use "F j" (e.g. May 31) as input format - I can live with this but what is worse, I cannot use "F j" or any other display format. This means my dates are always displayed as e.g. "Thursday, May 19, 2011" no other format is possible it seems because I have tried a few. In addition the input format "F j" seems to throw away any data entered when I save the form. My guess is because there is no year part specified, it fails silently (although I would expect a reasonable default like 1900 to be used to allow such a format to be stored.) I am happy to provide a login to a test system if it would be helpful.

Any help will be appreciated.

Anonymous’s picture

Anonymous (not verified) commented
Version: 7.x-2.0-alpha3 » 7.x-2.x-dev

KarenS,

I just saw your comment asking for detailed instructions. I am willing to provide you with the necessary assistance to reproduce and resolve this issue.

First off, i setup a test system and created a test content type I called date-module-test. To keep it simple I just created one additional field called hh_mm to represent TIME in hh:mm am/pm.

I used a Date datatype and used custom select widget type. I created a node to test data input and show that it infact does not work. I have other examples that I have tested but perhaps finding this issue will fix those too so i will keep it short for now.

Please note that this is a fresh install with no other contributed modules i.e. default core installed modules + date are the only modules installed.

You can access the system here http://www.sandbox.ryn-ventures.com. What is the best way to share the username and password with you?

Thanks in advance.

karens’s picture

karens commented
Status: Active » Closed (cannot reproduce)

First of all, this issue has been switched between D6 and D7, which has totally polluted it. The code in those versions is totally and completely different.

Second, there seems to be a lot of confusion between 'input format' and 'Display format'. The input format is what you set to control the format on the form entry. The Display format was actually getting superseded by whatever was set in the Display Fields screen, and has been removed from the latest code.

Third, If you have a field that has a year you have to use an input format that contains a year or you will get odd results. If the user does not input the year you it might end up as year 0001 or who knows what.

The input format field works fine in the latest D7 code. Please don't switch this back to a D6 issue again and try to reopen it as a D6 issue, that's not the way the issue queue is supposed to work.

karens’s picture

karens commented
Priority: Major » Normal

Also not really major either.

asb’s picture

asb commented

Related: #668688: Dates extracted are incorrect