DrupalKernel::getModuleFileNames

protected DrupalKernel::getModuleFileNames() Gets the file name for each enabled module. Return value array Array where each key is a module name, and each value is a path to the respective *.info.yml file. File core/lib/Drupal/Core/DrupalKernel.php, line 1368 Class DrupalKernel The DrupalKernel class is the core of Drupal itself. Namespace Drupal\Core Code protected function getModuleFileNames() { $filenames = array(); foreach ($this->moduleList as $module => $weight) {

DeleteForm::$taxonomyTerm

The taxonomy term being deleted. Type: \Drupal\taxonomy\TermInterface File core/modules/forum/src/Form/DeleteForm.php, line 20 Class DeleteForm Builds the form to delete a forum term. Namespace Drupal\forum\Form Code protected $taxonomyTerm;

ViewUI::addFormToStack

public ViewUI::addFormToStack($key, $display_id, $type, $id = NULL, $top = FALSE, $rebuild_keys = FALSE) Add another form to the stack; clicking 'apply' will go to this form rather than closing the ajax popup. File core/modules/views_ui/src/ViewUI.php, line 379 Class ViewUI Stores UI related temporary settings. Namespace Drupal\views_ui Code public function addFormToStack($key, $display_id, $type, $id = NULL, $top = FALSE, $rebuild_keys = FALSE) { // Reset the cache of IDs. Drupal ra

BreakLockForm::$tempStore

Stores the user tempstore. Type: \Drupal\user\SharedTempStore File core/modules/views_ui/src/Form/BreakLockForm.php, line 28 Class BreakLockForm Builds the form to break the lock of an edited view. Namespace Drupal\views_ui\Form Code protected $tempStore;

views_ui_view_preview_section_handler_links

views_ui_view_preview_section_handler_links(ViewExecutable $view, $type, $title = FALSE) Returns contextual links for each handler of a certain section. @TODO Bring in relationships Refactor this function to use much stuff of views_ui_edit_form_get_bucket. Parameters $title: Add a bolded title of this section. File core/modules/views_ui/views_ui.module, line 154 Provide structure for the administrative interface to Views. Code function views_ui_view_preview_section_handler_links(ViewExecutab

MarkupTrait::create

public static MarkupTrait::create($string) Creates a Markup object if necessary. If $string is equal to a blank string then it is not necessary to create a Markup object. If $string is an object that implements MarkupInterface it is returned unchanged. Parameters mixed $string: The string to mark as safe. This value will be cast to a string. Return value string|\Drupal\Component\Render\MarkupInterface A safe string. File core/lib/Drupal/Component/Render/MarkupTrait.php, line 34 Class Mark

SearchPageRepositoryInterface::getDefaultSearchPage

public SearchPageRepositoryInterface::getDefaultSearchPage() Returns the default search page. Return value \Drupal\search\SearchPageInterface|bool The search page entity, or FALSE if no pages are active. File core/modules/search/src/SearchPageRepositoryInterface.php, line 40 Class SearchPageRepositoryInterface Provides the interface for a repository Search Page entities. Namespace Drupal\search Code public function getDefaultSearchPage();

UrlGenerator::setContext

public UrlGenerator::setContext(SymfonyRequestContext $context) File core/lib/Drupal/Core/Routing/UrlGenerator.php, line 92 Class UrlGenerator Generates URLs from route names and parameters. Namespace Drupal\Core\Routing Code public function setContext(SymfonyRequestContext $context) { $this->context = $context; }

Statement::fetchCol

public Statement::fetchCol($index = 0) Returns an entire single column of a result set as an indexed array. Note that this method will run the result set to the end. Parameters $index: The index of the column number to fetch. Return value An indexed array, or an empty array if there is no result set. Overrides StatementInterface::fetchCol File core/lib/Drupal/Core/Database/Statement.php, line 79 Class Statement Default implementation of StatementInterface. Namespace Drupal\Core\Databa

Objected-oriented programming conventions

PSR-4, namespaces, class naming, and other conventions. A lot of the PHP code in Drupal is object oriented (OO), making use of PHP classes, interfaces, and traits (which are loosely referred to as "classes" in the rest of this topic). The following conventions and standards apply to this version of Drupal: Each class must be in its own file. Classes must be namespaced. If a module defines a class, the namespace must start with \Drupal\module_name. If it is defined by Drupal Core for use across