Included filters

A number of ready-to-use filters are included in the Freelinking framework (e.g. Nodetitle. Nid, User, Google search, Drupal search, Drupal projects, Wikipedia, etc.). This page describes the purpose of the included filters and how to use them.

The Freelinking link format is:

Backup and Migrate - with AWS S3

Backup & migrate module comes with built-in support for Amazon Web Services Simple Storage Service (AWS S3).

Putting your backups entirely offsite is probably one of the best things you can do for yourself and your clients. Making' local' backups is OK for development, but really doesn't help for disaster recovery of live websites.

You must have an AWS account set up first! Once you have that, and can log in to the AWS 'console' OK, we can proceed.

Advanced help

The contributed Advanced help module is an adjunct to Drupal's built-in Help system. It provides a framework that allows module and theme developers integrate help texts in a Drupal site, as well as exposing help to site administrators through the adminstrative interface.

Organizing Features

Features can play an important role in the configuration management of your site, and as the site grows it becomes increasingly critical to decide on a sensible organizational structure for features and stick to it. Otherwise, features can become entangled with one another, creating a messy web of dependencies and overlapping functionalities. This can be especially problematic in projects where several developers are working together.

Using Features to Manage Development

Features provides a centralized place to manage, configure and export components and write them to code. This convenience makes Features an excellent tool for managing changes between development environments and version control in conjunction with Git, SVN, or other version control systems.

This page lays out an example workflow for managing site development with Features:

Features: Moving Site Configuration to Code

Consider this scenario: you have created a custom content type on your local development server with several core and contributed field types specific to your application. Additionally, you have meticulously configured specific views for this content type, and created a custom user role that provides permission to add, edit, and delete content of this content type.

At this point, the content type lives in the database, not in code, so moving it to a remote server without overwriting the remote database presents quite a challenge. There are typically three ways to accomplish this:


Subscribe with RSS Subscribe to RSS - No known problems