Content Profile Views 3 integration [#670092]

The relationship handler for content profile make use of views_handler_relationship::options() to set the content type for the relationship.

This works for views 2, however views 3 doesn't support any more this way to define options.

The attached patch replace options() by option_definition() so, Content Profile can be used without problems in both, views 2 and views 3. (All handlers for views 2 in views module are using option_definition to set options)

Comment	File	Size	Author
	content-profile-option_definition.patch	710 bytes	dagmar

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Bilmar CreditAttribution: Bilmar commented 29 December 2009 at 19:27

Confirmed the issue in views 3 version. Patch applied smoothly and it fixed the issue. Thanks for the great work!

Comment #2

rburgundy CreditAttribution: rburgundy commented 4 January 2010 at 05:55

Status:

Needs review

» Reviewed & tested by the community

Tested and all was good. Content Profile is an awesome module and I hope this patch gets committed soon in preparation for views 3 support.

Comment #3

Bilmar CreditAttribution: Bilmar commented 5 January 2010 at 07:34

Hello,

For your reference, below are links to similar patches provided by dagmar in preparation for Views 3.
CCK - http://drupal.org/node/670344
Flag - http://drupal.org/node/673508

Thanks for the great work dagmar!