mattbk / uc_views_attribute_fork Goto Github PK

Not compatible with D7, don't need to upgrade it (in Ubercart core).

Not compatible with D7, don't need to upgrade it (in Ubercart core).

Not compatible with D7, don't need to convert.

This is the kicker for making this module much more useful. How to create a Views field for each attribute?

Can multiple handlers be added in the same handler file? If so, it could be possible to loop through the attributes array in uc_views_attribute.views.inc to create the view handler names, then loop through the attributes array in uc_views_attribute_handler_WHATEVER.inc to create the actual handlers. If all the handlers can be the same format (text, numeric, etc.) this could work.

There are two big ifs to look into above.

In uc_views_attribute.views.inc these views handlers are also defined:

• Model, uses views_handler_relationship
• Stock, uses views_handler_relationship
• uc_views_attribute_handler_field_combination.inc
• uc_views_attribute_handler_field_combination_price.inc, cost and sell price
• uc_views_attribute_handler_filter_attr.inc

https://trello.com/c/aBScCzzm/132-attributes

Take the names of the attributes from a table in the database. Then you join those on to the named array based on the attribute field unserialized in the View.

Translation (that was a voice memo):

• Determine how named attributes (not attribute values) are stored in the database
• Create an array of attributes by display name, from the database.
• Unserialize the attribute values stored on the product/order/whatever we're already looking at
• Create a Views Field for each named attribute in the database
• Match the attribute values to the Views fields based on name
• Display

For example, if you have two products with these attributes:

A Shirt

• Color
• Size

B Shirt

• Color
• Cut

and show them in the same table, values for both "Size" and "Cut" will be in the same column.

Thanks for this effort, I may have a chance to test it on a D6 to D7 upgrade shortly. I noticed one really minor issue (realizing these handlers are likely temporary until a better way to deal with them is worked out). The 'field_order_product_attribute07' handler is identical to the one for attribute06:

//Grab the value for the sixth attribute.
$result = $rows[5];

Should instead be:

//Grab the value for the seventh attribute.
$result = $rows[6];

When click sorting is added to a field in a table, it doesn't sort right.