We must use the date format from the field instance settings in some cases, but #1405010: How can a field handler access it's field instance settings?

Comments

Niklas Fiekas’s picture

Niklas Fiekas commented
Status: Active » Postponed
Niklas Fiekas’s picture

Niklas Fiekas commented
Component: Code » Code (Views)
Niklas Fiekas’s picture

Niklas Fiekas commented
Issue tags: +7.x-1.0 release blocker

Tagging.

Orbite’s picture

Orbite commented

Subscribe!

Niklas Fiekas’s picture

Niklas Fiekas commented
Status: Postponed » Active

Attacking this next.

Triumphent’s picture

Triumphent commented
Version: 7.x-1.x-dev » 7.x-1.0-beta1

Yes. When setting up an exposed birthday filter (Grouped filters), the value type cannot be configured to the second option: "An offset from the current time..." and automatically reverts to the first: "A specific date." Since the value in the field is something like -365, it results in an AJAX HTTP 500 error. Will hack into the module (sorry) and see if I can locate the problem. No guarantee though. :)

Triumphent’s picture

Triumphent commented
Version: 7.x-1.0-beta1 » 7.x-1.x-dev

Sorry, changed the version to beta 1 by mistake. Although it is apparent in the beta version too.

Triumphent’s picture

Triumphent commented
Issue summary: View changes

Rewrite

Triumphent’s picture

Triumphent commented
Issue summary: View changes

When is "next?"