Empower site builders and administrators with no-code tools to setup, enhance, configure, or maintain the site.

Context Domain

This is a simple Context condition plugin that lets you filter based on the domain.

Synonym term

For Drupal 7

English

Allows you to create human-readable URLs for terms and nodes.
After module is switched on the page adding/editing of the term will be available field "Synonym", using this field you can specify a synonym. When filling in the name of the term, the field "Synonym" is automatically filled (using Google Translate Api: translation from Russian to English). Synonym can be used to create human-readable URLs for terms or nodes on the page "patterns" of module Pathauto. On this page will be available two new patterns:
1) [node:node-synonym-path] to configure alias for nodes;
2) [term:term-synonym-path] to configure alias for terms.

If term has several parents, then alias will be created from the first parent, going on the list.
If node has several vocabularies/terms, as is the case with terms, alias will be created on the basis of the first term
the first vocabulary.

Example of use:

1) In the setting of pathauto for Taxonomy term paths for the vocabulary "Catalog" indicate a pattern:
catalog/[term:term-synonym-path].
For the type of node to which is added the vocabulary, specify a pattern
catalog/[node:node-synonym-path]/product[node:nid].html
2) Add a term to the vocabulary "Catalog": "мебель" (russian language). In the "Synonym" will appear automatically translate "furniture". Save.

URL IDs and Lazy URL ID Reference

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:

* Specification/wish list for better help system: http://drupal.org/node/1095012
* Better help system for Drupal 8: http://drupal.org/node/1031972
* Want the ability to create multiple outlines/maps: http://drupal.org/node/995370

Testing and Deployment Utility Scripts

version-upgrade-diff.sh upgrades Drupal by applying a patch created from two fresh copies of core.

Pages

Subscribe with RSS Subscribe to RSS - Administration tools