Search for all
| Title | Object type | File name | Summary |
|---|---|---|---|
| rdf_test.install | file | modules/ |
Install, update and uninstall functions for the rdf module. |
| rdf_test.module | file | modules/ |
Test API interaction with the RDF module. |
| rdf_test_install | function | modules/ |
Implements hook_install(). |
| rdf_test_rdf_mapping | function | modules/ |
Implements hook_rdf_mapping(). |
| rdf_test_rdf_namespaces | function | modules/ |
Implements hook_rdf_namespaces(). |
| rdf_theme | function | modules/ |
Implements hook_theme(). |
| Reader | class | misc/ |
|
| Reader.php | file | misc/ |
|
| Reader::$fileName | property | misc/ |
|
| Reader::$fileType | property | misc/ |
Mime-type in order to use zlib, bzip2 or no compression. In case ext-fileinfo is not present only the relevant types 'application/x-gzip' and 'application/x-bzip2' are assigned to this class property. |
| Reader::determineFileType | function | misc/ |
|
| Reader::determineFileTypeByHeader | function | misc/ |
In case ext-fileinfo is not present only the relevant types 'application/x-gzip' and 'application/x-bzip2' are resolved. |
| Reader::extractData | function | misc/ |
|
| Reader::resolveContainer | function | misc/ |
|
| Reader::resolveFourByteLittleEndian | function | misc/ |
|
| Reader::resolveManifestLength | function | misc/ |
|
| Reader::resolveStream | function | misc/ |
Resolves stream in order to handle compressed Phar archives. |
| Reader::resolveTwoByteBigEndian | function | misc/ |
|
| Reader::__construct | function | misc/ |
|
| ReaderException | class | misc/ |
|
| ReaderException.php | file | misc/ |
|
| README.md | file | misc/ |
Polyfill unserialize Backports unserialize options introduced in PHP 7.0 to older PHP versions. This was originally designed as a Proof of Concept for Symfony Issue #21090. |
| README.md | file | misc/ |
|
| README.txt | file | sites/ |
This directory structure contains the settings and configuration files specific to your site or sites and is an integral part of multisite configuration. The sites/all/ subdirectory structure should be used to place your custom and downloaded… |
| README.txt | file | sites/ |
Themes allow you to change the look and feel of your Drupal site. You can use themes contributed by others or create your own. WHAT TO PLACE IN THIS DIRECTORY? -------------------------------- Placing downloaded and custom themes in this directory… |
| README.txt | file | sites/ |
Modules extend your site functionality beyond Drupal core. WHAT TO PLACE IN THIS DIRECTORY? -------------------------------- Placing downloaded and custom modules in this directory separates downloaded and custom modules from Drupal core's… |
| README.txt | file | sites/ |
This directory should be used to place downloaded and custom libraries (such as JavaScript libraries) which are used by contributed or custom modules. |
| README.txt | file | profiles/ |
Installation profiles define additional steps that run after the base installation provided by Drupal core when Drupal is first installed. WHAT TO PLACE IN THIS DIRECTORY? -------------------------------- Place downloaded and custom installation… |
| README.txt | file | profiles/ |
This directory should be used to place downloaded translations for installing Drupal core. |
| README.txt | file | profiles/ |
This directory should be used to place downloaded translations for installing Drupal core. |
| README.txt | file | ./ |
CONTENTS OF THIS FILE --------------------- * About Drupal * Configuration and features * Installation profiles * Appearance * Developing for Drupal ABOUT DRUPAL ------------ Drupal is an open source content management platform supporting a… |
| README.txt | file | themes/ |
This directory is reserved for core theme files. Custom or contributed themes should be placed in their own subdirectory of the sites/all/themes directory. For multisite installations, they can also be placed in a subdirectory… |
| README.txt | file | themes/ |
ABOUT STARK ----------- The Stark theme is provided for demonstration purposes; it uses Drupal's default HTML markup and CSS styles. It can be used as a troubleshooting tool to determine whether module-related CSS and JavaScript are interfering… |
| README.txt | file | modules/ |
This directory is reserved for core module files. Custom or contributed modules should be placed in their own subdirectory of the sites/all/modules directory. For multisite installations, they can also be placed in a subdirectory… |
| README.txt | file | modules/ |
These files are useful in tests that upload files or otherwise need to manipulate files, in which case they are copied to the files directory as specified in the site settings. Dummy files can also be generated by tests in order to save space. |
| region.tpl.php | file | modules/ |
Default theme implementation to display a region. |
| REGIONS_ALL | constant | modules/ |
Return all regions. |
| REGIONS_VISIBLE | constant | modules/ |
Return only visible regions. |
| registry.inc | file | includes/ |
This file contains the code registry parser engine. |
| registry.test | file | modules/ |
|
| RegistryParseFilesTestCase | class | modules/ |
|
| RegistryParseFilesTestCase::$existing_changed | property | modules/ |
|
| RegistryParseFilesTestCase::$fileTypes | property | modules/ |
|
| RegistryParseFilesTestCase::$new | property | modules/ |
|
| RegistryParseFilesTestCase::getFileContents | function | modules/ |
getFileContents |
| RegistryParseFilesTestCase::getFiles | function | modules/ |
getFiles |
| RegistryParseFilesTestCase::getInfo | function | modules/ |
|
| RegistryParseFilesTestCase::setUp | function | modules/ |
Sets up a Drupal site for running functional and integration tests. |
| RegistryParseFilesTestCase::testRegistryParseFiles | function | modules/ |
testRegistryParseFiles |
| RegistryParseFileTestCase | class | modules/ |
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.