Site structure

Intro

This Drupal 6 module effectively creates a site-wide Views exposed filter for taxonomy terms. It creates an "exposed" View term filter displayed in a block as a <select>. One block can be created per vocabulary, then the filter used on multiple Views.

It was created in the Summer of 2010 for a client project. It has been tested and is currently running in a high traffic environment. I'll continue development if it is found useful for other sites. Let me know. Note: There are todo comments at the top of the module file.

Description

Each enabled taxonomy creates a block containing a
field listing the terms and a submit button. A View is created using a filter titled "Term default" and optionally a cache titled "Time-based Per Term".

When the form submitted, the selected term is saved as their default. When they access a View, their default term for the selected vocabulary is used to filter the View. Any number of Views can use the same filter.

Example use

Allow the user to select their current location, and filter to only show content related to that location.

Dependencies

1. Taxonomy
2. Views

Recommended

1. Session API: http://drupal.org/project/session_api

Concerns

See http://drupal.org/project/media_amazon instead...

The gnode project provides a new entity type that is specifically designed for the collection and storage of data that is intended to be displayed on maps. In the past, this has been accomplished in Drupal with CCK fields, but the use of an entity provides several advantages.

Features

• Provides database storage that is optimized for geo-searching.
• Standards based, and can accomodate any geometry type.
• Data storage can be shared by different mapping front-ends.
• Data services can be shared.

Gnode provides a new way for maps and geocoders to work with Drupal. Since data storage is provided at the entity level, maps and geocoders are not implemented as fields and views but as form elements that can be used on gnode pages, or theoretically on other types of pages as well. A full description of Gnode's features can be found at http://gnode.ccardea.com

Dependencies

Gnode requires the use of at least one other module to provide map services. Currently there is a module that provides Google maps and geocoders, a module that provides multipoint map views, and a module that provides proximity searching. These are implemented as separate projects.

Current Release

Drupal 8

What is it?

Adds trailing slashes to all URLs you want.
For example: example.com/user/.
This feature could be usefull for SEO motivations.

How do I install it?

Install and enable this module using one of the following methods:
https://www.drupal.org/docs/8/extending-drupal-8/installing-drupal-8-mod...

When you enable this module you haven't it in action yet.

Now you have to configure it. Read Configuration section for it.

Configuration

• To configure the module go to /admin/config/trailing-slash/settings
• On this page you have the option to enable/disable the configuration of this module
• List of paths
• Write a path per line where you want a trailing slash. Paths start with slash. It is also possible to add URLs with wildcards. (e.g., '/book', '/node/*')
• Enabled entity types
• You can choose the entity types that you want to have a slash, for example, the taxonomy terms of a particular vocabulary or nodes of a bundle

Requirements

• drupal::language
• php:7.1

Supporting organizations:

idealista Sponsorship of ongoing development.

Known Issues/Bugs

None.
If you found a new one, please, open it at https://www.drupal.org/node/add/project-issue/trailing_slash

Redirects from a node having a particular node reference field to the referenced node. Useful in situations when the node doesn't have a self-sufficient meaning.

Semantic Fields (formerly Semantic CCK in Drupal 6) was created to give users the abilility of customizing and enhancing the HTML