No further development

Sandbox to work on Views_send D7 port

On May 26th 2011 a new EU originated law came into effect that requires website owners to make significant changes to their sites and may fundamentally change the whole web browsing and shopping experience for everybody.This Cookie Law is amended privacy legislation that requires websites to obtain informed consent from visitors before they can store or retrieve any information on a computer or any other web connected device.

Overview

This module provides an easy and quick way to translate vocabulary terms. When using the Internationalization module to translate the terms of a vocabulary, you might find this very tedious and time consuming. The process will take you trough a couple of screens for each term you want to translate.

Meet "Translate Terms". This module will offer you a tabular overview of all "to be translated" terms as well as the functionality to translate on the fly, within the same screen.

Just a test project

Allows positioning of breadcrumb anywhere in the page

Exposes the breadcrumb page element in a way that lets us position it in regions.

This has now gone into core D8, so there is no further use for this module.

Probably not needed any more with better element handling in D7.
Just pushing this old code up here to the sandbox do it's got a namespace to refer to.

This module is an extension moving forward from 'Pathologic'
http://drupal.org/project/pathologic
By Garrett Albright

The Commerce Netherlands module provides one customisation for
Drupal Commerce (http://drupal.org/project/commerce) that allow it to
be better suited for deployment in the Netherlands.

Currently in Drupal Commerce the default Dutch Currency display is 10,00 €.
This module changes the display so that it is €10,00 (as most Dutch people expect)

Drupal Commerce Feature containing Dutch VAT settings:
- 6% BTW laag
- 19% BTW hoog

Requirement
commerce_features-7.x-1.x-dev (2012-Mar-17)

Common issues when using two VAT rates
both taxes applied to every product
For those who are struggling with both taxes being applied to all products instead of just one tax rate per product:

An example of reading and updating a field on a Entity.

Requires Profile2 and there being a field called field_status on the main profile2 type.

Provides a Rules action for granting Userpoints based of the quantity for a certain product type in a Commerce order. ie. Allows you to sell a "points/credits" product and then grant users userpoints based on the quantity of the product within the order.

Provides a new Rules action called "Grant points to a user based on quantity of items in an order", which will read how many of a given product type (which is selectable) are within an order and grant that many points to a given user.