Note: As of 2021-06-16, this project appears to no longer be supported. If you are interested in taking this project over, or you as the project maintainer feel this message has been posted in error, please reply to #3214225: Subdomain appears to be unsupported.
Easily create subdomains per user, taxonomy term, content type, or organic group. This module adds an easy text field to the entity where you can enter a subdomain for it.
User: e.g. "Mary" and all of her content at http://mary.example.com
Taxonomy: e.g. "Seattle" and all content tagged with it at http://seattle.example.com
Organic Group: e.g. "MyGroup" and all of its content at http://mygroup.example.com
Content type: e.g. "News" content type and all of its nodes at http://news.example.com
The geonames_cck module implements a CCK field type that uses geonames (http://www.geonames.org) to translate location names into their longitude and latitude coordinates.
This module was designed to work with the geomap (http://drupal.org/project/geomap) module. Locations are output using Geo microformats, and the geomap module will display any geo data on a google map.
The Outline Designer is a user experience module that makes book management more intuitive. Essentially it overlays on the admin book outline page so that you can use AJAX to build and edit site outlines much faster then Drupal traditionally allows.
6.x-2.x branch (Upgrading from 1.x to 2.x)
If you are upgrading from the 1.x branch, uninstall 1.x and then add the 2.x version. Removing the original files will help keep things cleaner down the road as things have been shifted around based on best practices. There is no database work done so an upgrade should be as easy as uploading the module and running the modules page (hitting submit at the bottom).
7.x-2.x branch
This branch is in active development. Please help out by testing out the nightly devs and submitting patches. This is a direct port of the 6.x-2.x branch with some minor tweaks to make it work with drupal 7. It definitely has bugs still but can at least be installed for testing.
A CCK field type to store lists of co-ordinates, or tracks. These tracks are intended to be visualised on maps, plotted as distance/altitude profiles, have statistics derived from them, etc.
The module has been created in what is hoped is a flexible enough manner to allow multiple input formats to be used, and to allow track data to be shown in many different ways. The 'base' trackfield CCK field knows about latitude, longitude, altitude and distance. This system is flexible enough to allow distance/altitude pairs to be entered without latitude/longitude (this entry could be via the trackfield_csv module). This would be useful for someone with a cycle computer with altimeter but no GPS who wishes to graph hill profiles. Although of course the input modules know how to convert latitude/longitude pairs into distance data when it is entered.
User data handling will be catered for later, an example of which is an athlete who might want to record heart rate and time information (from which speed can be derived) at each co-ordinate.