Under active development

Back up and restore your Drupal MySQL database, code, and files or migrate a site between environments. Backup and Migrate supports gzip, bzip and zip compression as well as automatic scheduled backups.

With Backup and Migrate you can dump some or all of your database tables to a file download or save to a file on the server or offsite, and to restore from an uploaded or previously saved database dump. You can choose which tables and what data to backup and cache data is excluded by default.

Overview

This module allows you to add autocomplete functionality to virtually any fields of a Drupal site. During the input, the field will be expanded and offer a list of suggestions before you start the search.
By default, the module integrates with search forms from the Drupal core Search and Search Block.

Optionnal: use views module to create your own suggestion set easily.
Optionnal: use transliteration module to build suggestions regardless of special characters (é, è, ç, etc...)

Features

• Autocomplete virtually any form in your website using id selector.
• Uses either static data, external or internal URL callback or an embeded view style to easily create your suggestions set.
• Forms to autocomplete are individually configurable
• Many css styles embedded, or just add your own one
• Using the embeded Views format (requires Views) any type of suggestions can be used:
  - words (any word in your site)
  - node titles
  - comment titles (if optional module comment enabled)
  - taxonomies (if optional module taxonomy enabled)

- ....

What is it?

This module provides a block which lists relevant content. This is done using Presets to provide configuration to filter for specific content types and vocabularies and to limit the maximum size. The result are a list of nodes which the module considers most relevant based on the categorization of the current page. This is achieved by finding other nodes which contain the most amount of taxonomy terms in common.

The older Drupal 6 module provided this as Block and a CCK Field Type, however given the direction Drupal is taking with Layout Builder I have currently opted to for just a Block. Each preset is its own exportable configuration entity so can be exported and managed through Configuration Management. Each Preset gets its own block you can place.

The Drupal SEO Checklist uses best practices to check your website for proper search engine optimization.

The Builder modules is an experiment in generating drupal code from specifications provided as YAML files. With this module, I seek insight into how far the new reflection mechanisms like the Schema API and the Form API carry.

There is an example YAML spec for a node module in the config/ directory. The file specifies a set of content types in the types section.

I have deliberately refrained from providing a graphical user interface to specify things. For incremental updates, this is a limitation in that I won't be able to track what exactly has changed from one version of a YAML file to the next and e.g. automatically generate update functions for the installer. Because of this limitation, I do not consider this module a competition to the CCK or Views projects.

On the other hand, this module could be used to bootstrap a new generation of more complex modules like CCK and Views by generating the necessary metadata store for these.

Currently, the Builder module is able to generate node modules with simple field types. The boiler plate for the various hook implementations is mainly taken from the node example, but updated to use the new Schema API in Drupal 6. I consider the module an early Alpha version due to its functional limitations.

Associate menus with Organic Groups.