Maintenance fixes only

GUFF provides an automated way of dealing with entities with a field field, through Features.

Module providing unique URLs for particular product variations referenced by one product display. (A temporary solution for issue #1082596: Implement unique URLs for particular products on product displays.)

• For each product it provides id parameter, for example:
  http://www.mycommercesite.com/node/1?id=1
  http://www.mycommercesite.com/node/1?id=2
  as well as sku parameter, for example:
  http://www.mycommercesite.com/node/1?sku=pr1
  http://www.mycommercesite.com/node/1?sku=pr2
• For product types with extra fields enabled to function as an attribute field for Add to Cart forms, it provides option to use values of those fields to select specific product variation.

  For example, if a product type has a Term reference field with machine name field_color, and product has a term tid = 2, name = Red selected, then such product variation could be displayed using either:
  http://www.mycommercesite.com/node/1?color=Red (note this is case-sensitive), or:
  http://www.mycommercesite.com/node/1?color=2

The Performance and Scalability Checklist is an interactive checklist of performance and scalability optimization tasks for Drupal. It will help you optimize the software stack your web site operates on, from Apache up to your Drupal theme.

This tiny module removes the requirement for fields to have machine names starting with field_.

Views row operations provides a new views field which allows you to add buttons to a view row that trigger operations on that row. It extends the power of Views bulk operations so that each button can be configured in a very similar way to bulk operations.

Rationale: Less is more

Views bulk operations is an awesome module, which is designed to allow operations to be applied in bulk to a view. It's user interface is well suited for this objective, but it is a bit long-winded when you just want to apply an operation to only one item in a view.

The purpose of this module therefore is simply to reduce the number of clicks a user needs to perform in order to execute a 'bulk' operation on only a single row. With Views bulk operations, this can take up to 4 clicks and some scrolling: For example, if your operations are in a select drop down:

1. select the row, then scroll back to the top
2. open the select drop down
3. choose the operation
4. then click 'Execute'.

If you're using buttons for your bulk operations, there are less clicks (2), but still potentially a bit of scrolling.

With Views row operations, a user can simply find the row in the view and click a button in the row to perform an operation on that item: 1 click!

Usage