I updated to the 6.x-2.x-dev and now relative value date defaults I set in my View display are not being applied to my date field exposed filter in a View. I am using Views 6.x-2.12

After checking out the git repo it seems there were some changes to how the date_api handles the default date, but I do not have enough knowledge of the surrounding code to completely understand what is going.

I wish I could help fix this but learning the ins and outs of the date module will be time consuming for me.

Comments

ice5nake’s picture

ice5nake commented

Actually I should also mention that I had a similar problem with this in the previous version. Previously the default value would be applied to the listing but not displayed. Now it is not even applied to the listing.

As well, the previous version I was running would display the defaults on subsequent searches if I was an authenticated user.

ice5nake’s picture

ice5nake commented

I have reverted to 6.x-2.7. I discovered that when I set this filter to "Optional" the default information is used. This is not mentioned in the "Configure filter" information anywhere within the View display settings. I found this very peculiar and assume this is still a bug and not working as intended.

danielstrum’s picture

danielstrum commented
Version: 6.x-2.x-dev » 6.x-2.8

I have changed this to an issue with 6.x-2.8. This bug has made this version unusable for me as I now have a list of hundreds of items instead of maybe 10 (I was limiting the default filter to 3 months back from "now" on a site that has 7 years of content). Since 2.7 has a security issue, this puts me in a bad position. I have reverted to 6.x-2.7 but would love a workaround. Working on the code is beyond my ability or I would try to help. Thanks.

arlinsandbulte’s picture

arlinsandbulte commented

Just a note:

While I don't mean to diminish the importance of fixing security holes, the security issue fixed in Date 6.x-2.8 is, IMO, not something most sites will need to worry about:
http://drupal.org/node/1401434

From the security announcement:

This module enables you to add and administer date fields to nodes. It includes Date Tools, that allows users to convert nodes created with the Event module into Date fields. The conversion form for Events is vulnerable to SQL injection.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer Date Tools", and the option is only available on sites which have used the Event module in the past and have the Event table in the database.

So, only if you have Date Tools enabled, & only if you used the Event module in the past, and only if you have an inexperienced or untrusted user with the role "administer Date Tools" will this security issue be any concern to you.

danielstrum’s picture

danielstrum commented

Yes... This is why I am still able to use 6.x-2.7. I do appreciate your note... thanks for posting it. The main issue for me right now is the the site sends out security update notices so, if there is a "real" update needed, it is not obvious (def a minor issue). However, moving forward, I hope this bug is fixed in the next version. Thanks for all your work!

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
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.