Minimally maintained

This module's audience is developers who require machine names for taxonomy vocabularies, including views support. This module allows existing (and new) installations to continue using the Drupal 6 taxonomy API while gaining the benefits of vocabulary machine names.

As such, it should play nice with any taxonomy related modules (such as those that provide import / export features, etc...)

Background

Taxonomies are a bit of an issue to deal with in Drupal, specifically in terms of using them in install profile or update hooks, team development, and deployment through environments.

There are a few modules out there which try to get around this issue. However, they are limited in a number of ways. Currently there are 3 methods I can see in trying to solve this. This module goes with #3.

1. Use existing modules (such as features_extras or exportables). This provides taxonomy (among other) machine name support, however, it can require multi-module dependencies, and typically require additional calls while programming. As well, there is typically no views support to remove "vid"s from view exports.

Flag lists allows regular users to create unlimited private flags called lists. Flag lists extends Flag. In Flag, a site administrator creates the flags that any authorized users may use.

Put your site in maintenance mode by uploading a file.

This module adds support for mixed use of SSL and non-SSL (http and https protocols) for the 6.x branch of Domain Access.

Currently, Domain Access allows you to specify per domain whether to use http or https, and if a domain source is configured, URLs throughout that site (including form actions and so forth) use that protocol. However, if your site mixes use of both protocols (say, with SSL to protect the user login page, admin pages, or authenticated sessions in general), Domain Access does not support that configuration.

For background information, see the original issue: #758714: Allow both http and https for a given domain?

Features Override is used to change (override) existing Features. You may want to use it if:

• You are installing a feature module that requires this module.
• You have a site built on features - e.g., an Open Atrium or Commerce Kickstart site - and you want to make changes without losing them when you upgrade to a new version.
• You are a feature developer looking to selectively override components (Views, content types, etc.) of existing features and export just the changes to code.

Initial 1.x development sponsored by Chocolate Lily. The 7.x-1.x branch was unstable with several reported issues for views (and, likely, panels). That branch has been abandoned with new development occurring in the 7.x-2.x branch (sponsored by Phase2 Technology). Drupal 6 users should continue to use the 6.x-1.x version...no 2.x branch is planned.

NOTE: Overrides exported with version 1.x are NOT COMPATIBLE with overrides exported with version 2.x. If upgrading you should disable the 1.x override, remove the 1.x Features Overrides module, install/enable the Features Overrides 2.x version, then re-export your changes as new overrides.

Drupal 8

For similar functionality in Drupal 8, please see the Config Actions module.

Requirements

• Features 7.x-1.0-rc1 or later, to include the fix to #984472: Add hook_node_info_alter.
• CTools

This module is no longer under development due to duplicate functionality: Field collection module.