Articles

Drupal 8 comes with three field formatters for text fields: Default, Trimmed, and Summary or Trimmed.

The following modules provide additional Field Formatter plugins for text fields:

Fields with plain text or string types have only one field formatter in core: the default. It simply displays the unaltered string, potentially linked to its parent entity.

Below is a list of contributed modules that provide additional field formatting options for text fields:

In Drupal, configuration refers to the set of administrative settings that define how the site functions, rather than the content of the site itself.

Configuration typically includes things like the site name, content types and their fields, taxonomy vocabularies, views, and so on.

Drupal stores site configuration data in a consistent manner—from the list of enabled modules to content types, taxonomy vocabularies, fields, and views.

Making configuration changes directly on a live site is not recommended. The configuration system is designed to make it easy to use the current configuration, test changes locally, export them to files, and then deploy them in a production environment. Your site’s configuration can be stored as part of your codebase and integrated into version control.

Here’s a simple example demonstrating how a site name can be configured in one environment and deployed in another. This example involves manually uploading and downloading .tar.gz configuration files, but it’s also possible to keep your site’s sync directory under version control and synchronize that way.

1. Install Drupal 8. We’ll refer to this as the “Production” site.

This page assumes you’re familiar with using Drush and have the latest version installed.

The following example demonstrates how to export changes from development sites to production sites. The reverse is also possible.

1. Install Drupal 8. We'll refer to this site as "Live".

By default, Drupal places the configuration synchronization directory within the site's files directory, using a hash as part of the folder name, for example: sites/default/files/config_HASH.

The HASH is a long string of random characters. This makes accessing configuration via the web more difficult (though not impossible). The sync directory location can be changed after installation.

Note that by default, Drupal stores configuration management data in the database. To enable a file-based workflow, you must modify both settings.php and services.yml.

This must be done before installing Drupal, as switching back to database-based configuration after enabling file-based storage is complex. If you need to enable configuration in files after site installation, you must first export your configuration and save a copy in the active config directory before enabling file-based config management.

You’ve built a Drupal 8 site and want to host it on your server
or
You’ve set up a Drupal 8 site on your remote server and want to work on it locally

Drupal 8 is Different

Up until Drupal 7, it was a relatively simple process: copy all the files, copy the database, and you're good to go.
With Drupal 8, CMI – Configuration Management Interface – comes into play and must be handled appropriately.

Drupal includes a feature that allows you to serve separate, independent websites from a single codebase. Each site has its own database, configuration, files, and base domain or URL. While this documentation is still being expanded, please refer to the relevant documentation for Drupal 7 in the meantime.