This simple module allows you to associate a currency codes with your site locales. To use it, simply visit Site configuration -> Languages (/admin/settings/language/overview), and edit each of your locales. With this module enabled, you will see a new field entitled 'currency' which you can use to define the currency using an ISO 4217 compliant currency identifier. Examples: "GBP", "EUR", and "USD".
This module alters the core languages database table, adding an additional column named currency. This ensures that the currency data will always be loaded along with $language objects without any additional overhead. A convenience function locale_currency_get_currency() enables you to quickly find out the currency code associated with a particular locale.
Code examples
global $language;
print 'Current currency is: '.$language->currency;
$french_currency = locale_currency_get_currency('fr');
print 'French currency is: '.$french_currency->currency;
Customisations
Locale Currency is being developed by Tom Kirkpatrick (mrfelton) of SystemSeed. The author may be contacted for paid customisations of this module, Drupal consultation or other Drupal-related projects.
The URL ID module provides a field that gives an entity a 'global' ID, based on the domain name, entity name and entity id (such as http://example.com/node/1).
The idea is that remote entities can be downloaded, inheriting the remote URL ID – a node could have the URL ID 'http://example2.com/node/123'.
The Lazy URL ID Reference module provides a lazy-loading reference field, utilizing URL IDs. The idea is to refer to a URL ID such as 'http://example2.com/node/123'. If there is a local entity with this URL ID, the reference field will point to it (eg. node/456), if not, it will point to the remote source (eg. 'http://example2.com/node/123').
Furthermore, URL ID fields have fetchers – plugins that allow fetching remote data and saving it locally. These fetchers can also affect the reference link, for example by automatically download the referenced entity, or to redirect to the remote source.
This is a work in progress. It is related to a project for being able to download and sync help pages from drupal.org to your local site. See the following links for more information: