Site structure

 
This may be completely dropped in favor of http://drupal.org/project/location_taxonomize

Bundle Copy for Drupal 8

Bundle Copy is in Drupal 8 Core CMI!

The Search API spatial module (7.x-2.x branch) adds the possibility of location based searching to the Search API module.
D7: Currently only Apache Solr is supported as the service class.
D8: Search API Solr works and is fully tested. Elasticsearch connector should work, but problems may arise as this was not fully tested.

Requirements

• a content type/entity with a latitude/longitude field (currently geofield is supported, location fields probably work, but I haven't tested it yet)
• Apache Solr server 3.1+ (I only tested with 3.3 and 3.4, but spatial search is included since 3.1)
• Current versions of Search API and Search API Solr

Installation and configuration

• Put the module in sites/all/modules folder.
• enable the module and any sub-module(s) you want
• add/modify a Search API index which lies on a Solr server
  • on the index's "Fields" tab: index the field containing the latlng value ("LatLong Pair") and select the "Latitude/longitude" type.
    If you don't see the field, check the "Add related field" form at the bottom of the page (see screenshot 1 and screenshot 2)

The basic idea is to provide a module that allows for designing of steps, e.g. for a registration process on a site with the flexibility to tie together different components. This will be achieved by providing node independent steps, which can be created, increased, decreased, reset and of course manipulated via an API-like approach, which means you may well put a simple PHP one liner in a block which provides for step increment as well as a target node to lead the user to upon clicking the link User Steps generates.

Dependencies so far:

• Token module
• Data module

** This project is currently for drupal-6.x, but should be (once finished and shiny) not pose much trouble for a D7 port **

** CO-MAINTAINERS WELCOME **

ALREADY WORKING:

• define up to 10 steps, each with a link to a certain node
• let User Steps generate link to progress to the next step
• create a custom link with a custom increment (e.g. user may override a step if undesired and new step value will be saved to database)
• token support for target nodes (or custom content), so you may send a user to /user/[uid]/edit for example
• storage of user steps in a custom table, achieved via Data module

Cities and States from Brazil.

This my first project.