In Depth Guide : Acquia Certified Developer Drupal
  • IN DEPTH GUIDE: ACQUIA CERTIFIED DEVELOPER - DRUPAL 8 EXAM
  • Test Format
  • Domain 1.0: Fundamental Web Development Concepts
    • 1.1 Demonstrate knowledge of HTML and CSS
    • 1.2 Identify Javascript and jQuery programming concepts
    • 1.3 Demonstrate the use of Git for version control
  • Domain 2.0: Site Building
    • 2.1 Demonstrate ability to create and configure Content Types with appropriate fields and field sett
    • 2.2 Demonstrate ability to configure Display Modes for building custom form and view modes for core
    • 2.3 Demonstrate ability to create and use Taxonomy vocabularies and terms for classification and org
    • 2.4 Demonstrate ability to configure Block types, manage Blocks library and configure Block layouts
    • 2.5 Demonstrate ability to build main and alternative navigation systems by using Menus
    • 2.6 Demonstrate ability to create and configure Views for building content list pages, blocks and fe
    • 2.7 Demonstrate ability to use Configuration Management capabilities for exporting site configuratio
    • 2.8 Demonstrate ability to build multilingual websites using core multilingual capabilities
    • 2.9 Demonstrate ability to build RESTful web application using core Web Services capabilities
  • Domain 3.0: Front end development (theming)
    • 3.1 Given a scenario, demonstrate ability to create a custom theme or sub theme.
    • 3.2 Demonstrate knowledge of theming concepts
    • 3.3 Demonstrate ability to use Twig syntax
    • 3.4 Demonstrate ability to build or override Twig templates for defining layout content
    • 3.5 Demonstrate ability to write template pre-process functions for overriding custom output
  • Domain 4.0: Back end development (coding)
    • 4.1 Demonstrate ability to write code using core and Object Oriented PHP
    • 4.2 Demonstrate ability to develop Custom Modules using Drupal API for extending Drupal functionalit
    • 4.3 Demonstrate ability to store and retrieve data using code
    • 4.4 Demonstrate ability to work with other essential APIs
    • 4.5 Demonstrate ability to write code using Drupal Coding Standards
    • 4.6 Demonstrate ability to analyze and resolve site performance issues arising from site configurati
    • 4.7 Demonstrate ability to analyze and resolve security issues arising from site configuration or cu
  • Other Resources
Powered by GitBook
On this page
  • Use core's development debugging tools
  • Writing to logging API
  • Other Resources
  1. Domain 4.0: Back end development (coding)

4.6 Demonstrate ability to analyze and resolve site performance issues arising from site configurati

Previous4.5 Demonstrate ability to write code using Drupal Coding StandardsNext4.7 Demonstrate ability to analyze and resolve security issues arising from site configuration or cu

Last updated 7 years ago

Review admin logs and status reports. Review how to write to the logging API.

The Logging system will help monitor a site to report any problems. Navigate to /admin/reports/dblog

The Status report on the site also provides valuable information about site configuration. Navigate to /admin/reports/status.

A site admin can also configure what type of errors to display on a page. Error messages should never be displayed on a production site.

From the command line drush status will also provide the same valuable information.

drush @site-alias status
drush @site-alias ws

Drush ws will also print out messages to the terminal.

Use core's development debugging tools

Drupal 8 ships with an example.settings.local.php. Inside this file there are lots of debugging goodies. For example, turning off caching, increasing your error levels and enabling local services.

In this file there are examples of how to set the display error level to verbose

$config['system.logging']['error_level'] = 'verbose';

Sometime a page can be caching and causing an error, disable cache and clear the page cache.

/**
 * Disable CSS and JS aggregation.
 */
$config['system.performance']['css']['preprocess'] = FALSE;
$config['system.performance']['js']['preprocess'] = FALSE;

Writing to logging API

When writing custom modules you can write to the logging API. For example

\Drupal::logger('my_module')->error($message);
$logger->log($level, $message);

Other Resources

Drupal.org Security