Closed (fixed)
Project:
Flag
Version:
6.x-1.x-dev
Component:
Views integration
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Jan 2010 at 04:13 UTC
Updated:
22 Jan 2010 at 04:50 UTC
With views 3, handler::options(&$options) to define the options for a handlers is not supported anymore.
I have noticed that flag use option_definition for relationships handler but still use options() for field and filter handlers. This produce that options for these handlers were not configurable when views 3 is used.
This patch fix that, views 2 integration should work without problems.
| Comment | File | Size | Author |
|---|---|---|---|
| flag-views-3.patch | 1.2 KB | dagmar |
Comments
Comment #1
quicksketchThanks dagmar! So if I'm understanding this correctly, the options() method still works in Views 2, even for field and filter handlers?
Comment #2
dagmarHi quicksketch, yes options() works for views 2 (but not for views 3), however options_definition works for views 2 and 3 without problems.
Comment #3
Bilmar commentedPatch applied smoothly and the issues I was experiencing with Flag in Views 3 was resolved.
Flag is definitely an essential module and I'm glad that this patch will allow me to move to Views 3 when released.
@dagmar - If possible, could you please look into if User Relationships module http://drupal.org/project/user_relationships requires updating for Views 3 as well? Thanks for the great work!
For quicksketch's reference, below are links to other modules updating to options_definition for Views 3.
CCK - http://drupal.org/node/670344
Content Profile - http://drupal.org/node/670092
Comment #4
rburgundy commentedtested and works great. i'm really wanting to move to Views 3 even as dev version as the new features are great.
hope we can get these patches committed with the help of the community
Comment #5
quicksketchTested with Views 2 and it continues to work just fine. Thanks dagmar! Committed to both 1.x and 2.x versions.