Please re-classify as bug report or feature request if appropriate ...

In the process of updating from an earlier version (around Sep 4) to the current 4.7 version I seem to have lost the ability to have 12-hour and am/pm selectors. It now uses a 24 hour selector.

  • Is there a way to revert to the 12-hour and am/pm selectors?
  • Does the input format defined under "Advanced input options" have any effect when using the select list widget?
  • If not, is there an easy way to control the order of the selectors (I prefer the old default order)? I'm guessing it should be possible with theming but haven't yet looked into it.

Comments

karens’s picture

karens commented

The input format controls all of that now. You can select a different option to change the order, or put in custom code for the date string. One nice thing about this new code is that you can control the order for jscalendar and text fields, too, so you can input dates as mm/dd/YYYY instead of in the iso format.

karens’s picture

karens commented
Status: Active » Fixed

I assume no response means this is taken care of :-)

RayZ’s picture

RayZ commented
Category: support » bug
Status: Fixed » Active

OK, I see that it does work. However there is a bug which threw me off. When I enter a custom input format, save it, and come back to the field settings, the custom input format field is blank. I originally assumed this meant that it was irrelevant for the select list widget so I didn't bother to check if it had modified the behavior of the widget.

Turns out the value is apparently being saved and used, just that the form isn't being re-populated correctly when you go to re-edit the field settings.

karens’s picture

karens commented

I can't replicate this problem in latest version. The input format saves correctly for me. Do you still have a problem with the latest code?

karens’s picture

karens commented
Status: Active » Fixed

I'm assuming this is since fixed. Reopen if not.

RayZ’s picture

RayZ commented

I'm sorry, I have just been swamped and don't have the same test setup where I first encountered the problem, so I wasn't able to double-check. It's probably fair to assume it's fixed.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)