That big blue field is a whole bunch of cachegrind.out files in /private/var/tmp. Turns out these files are generated when you have Xdebug enabled, which I do because it's useful to debug PHP as a developer. So, first thing I try to do is delete all these useless files.
I changed where Xdebug saves it's cache files to /tmp in my php.ini file. In my case with MacPorts it's at /opt/local/etc/php54/php.ini.
That big blue field is a whole bunch of cachegrind.out files in /private/var/tmp. Turns out these files are generated when you have Xdebug enabled, which I do because it's useful to debug PHP as a developer. So, first thing I try to do is delete all these useless files.
I changed where Xdebug saves it's cache files to /tmp in my php.ini file. In my case with MacPorts it's at /opt/local/etc/php54/php.ini.
X-ray module gives a look at the skeletal structure of a site to help developers and site builders see how things work. X-ray Features A technical summary is added to the help above the main administrative sections. For example, blocks, content types, and menus are summarized on Structure; themes on Appearance; etc. A table of permission titles matched to their permission machine names. A table of most* hooks which Drupal invokes (and when they are invoked) and that are available to be implemented. The function and arguments producing each page you visit, displayed on that page.
X-ray module gives a look at the skeletal structure of a site to help developers and site builders see how things work. X-ray Features A technical summary is added to the help above the main administrative sections. For example, blocks, content types, and menus are summarized on Structure; themes on Appearance; etc. A table of permission titles matched to their permission machine names. A table of most* hooks which Drupal invokes (and when they are invoked) and that are available to be implemented. The function and arguments producing each page you visit, displayed on that page.
X-ray module gives a look at the skeletal structure of a site to help developers and site builders see how things work. X-ray Features A technical summary is added to the help above the main administrative sections. For example, blocks, content types, and menus are summarized on Structure; themes on Appearance; etc. A table of permission titles matched to their permission machine names. A table of most* hooks which Drupal invokes (and when they are invoked) and that are available to be implemented. The function and arguments producing each page you visit, displayed on that page.
The Drupal Console is a suite of tools that you run on a command line interface (CLI) to generate boilerplate code and interact with a Drupal 8 installation.
The Drupal Console is a suite of tools that you run on a command line interface (CLI) to generate boilerplate code and interact with a Drupal 8 installation.
The Drupal Console is a suite of tools that you run on a command line interface (CLI) to generate boilerplate code and interact with a Drupal 8 installation.
This project aims to make spinning up a simple local Drupal test/development environment incredibly quick and easy, and to introduce new developers to the wonderful world of Drupal development on local virtual machines (instead of crufty old MAMP/WAMP-based development).
This project aims to make spinning up a simple local Drupal test/development environment incredibly quick and easy, and to introduce new developers to the wonderful world of Drupal development on local virtual machines (instead of crufty old MAMP/WAMP-based development).