Search for read
| Title | Object type | File name | Summary |
|---|---|---|---|
| PoStreamReader::$uri | property | core/ |
URI of the PO stream that is being read. |
| PoStreamReader::close | function | core/ |
Implements Drupal\Component\Gettext\PoStreamInterface::close(). |
| PoStreamReader::getHeader | function | core/ |
Get header metadata. |
| PoStreamReader::getLangcode | function | core/ |
Get language code. |
| PoStreamReader::getSeek | function | core/ |
Gets the pointer position of the current PO stream. |
| PoStreamReader::getURI | function | core/ |
Gets the URI of the PO stream that is being read or written. |
| PoStreamReader::open | function | core/ |
Implements Drupal\Component\Gettext\PoStreamInterface::open(). |
| PoStreamReader::parseQuoted | function | core/ |
Parses a string in quotes. |
| PoStreamReader::readHeader | function | core/ |
Read the header from the PO stream. |
| PoStreamReader::readItem | function | core/ |
Reads and returns a PoItem (source/translation pair). |
| PoStreamReader::readLine | function | core/ |
Reads a line from the PO stream and stores data internally. |
| PoStreamReader::setHeader | function | core/ |
Implements Drupal\Component\Gettext\PoMetadataInterface::setHeader(). |
| PoStreamReader::setItemFromArray | function | core/ |
Store the parsed values as a PoItem object. |
| PoStreamReader::setLangcode | function | core/ |
Set language code. |
| PoStreamReader::setSeek | function | core/ |
Sets the seek position for the current PO stream. |
| PoStreamReader::setURI | function | core/ |
Set the URI of the PO stream that is going to be read or written. |
| PoStreamReader::shortenComments | function | core/ |
Generates a short, one-string version of the passed comment array. |
| profiles.README.txt | file | core/ |
Installation profiles define additional steps that run after the base installation of Drupal is completed. They may also offer additional functionality and change the behavior of the site. WHAT TO PLACE IN THIS… |
| read-more.component.yml | file | core/ |
core/profiles/demo_umami/themes/umami/components/read-more/read-more.component.yml |
| read-more.css | file | core/ |
This file is used to style the more link. |
| read-more.twig | file | core/ |
<a{{ attributes.addClass('read-more').setAttribute('href', url) }}> {% block text %}{% endblock %} <span class="visually-hidden"> - {% block a11y %}{% endblock %} </span> <svg… |
| README.md | file | composer/ |
Drupal Recipe Unpack Plugin Thanks for using this Drupal component. |
| README.md | file | core/ |
Why do we need the updated_module fixtures? Because there is a need to thoroughly test the updating of a module. See \Drupal\Tests\package_manager\Build\PackageUpdateTest. |
| README.md | file | core/ |
This directory is used as the basis for quasi-functional tests of Package Manager based on \Drupal\Tests\package_manager\Kernel\PackageManagerKernelTestBase. It provides a bare-bones simulation of a real Drupal site layout, including: |
| README.md | file | core/ |
Drupal custom PHPStan rules This directory contains PHPStan rules specifically developed for Drupal. |
| 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 configurations. It is now recommended to place your custom and downloaded extensions in the /modules, /themes,… |
| README.txt | file | composer/ |
Composer-Ready Project Templates ================================ Thanks for using these Drupal project templates. You can participate in its development on Drupal.org, through our issue system: https://www.drupal.org/project/issues/drupal You can… |
| README.txt | file | composer/ |
# Drupal Metapackages A metapackage is a Composer package that contains only a composer.json, and has no other content. In other words, the purpose of a metapackage is to provide dependencies, not to provide code or data. ## Metapackages Provided… |
| README.txt | file | composer/ |
The Drupal Vendor Hardening Composer Plugin =========================================== Thanks for using this Drupal component. You can participate in its development on Drupal.org, through our issue… |
| README.txt | file | profiles/ |
Installation profiles define additional steps that run after the base installation of Drupal is completed. They may also offer additional functionality and change the behavior of the site. WHAT TO PLACE IN THIS… |
| README.txt | file | themes/ |
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 | modules/ |
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 | core/ |
ABOUT UMAMI ----------- Umami is the theme used for the "Umami food magazine" demonstration site. ABOUT DRUPAL THEMING -------------------- See https://www.drupal.org/docs/theming-drupal for more information on Drupal theming. |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for image files previously inherited from the Classy theme. WHY WERE CLASSY IMAGE FILES COPIED HERE? ------------------------------------------- Classy was removed in… |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for CSS files previously inherited from the Classy theme. WHY WERE CLASSY CSS FILES COPIED HERE? ------------------------------------------- Classy was removed in Drupal… |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for JS files previously inherited from the Classy theme. WHY WERE CLASSY JS FILES COPIED HERE? ------------------------------------------- Classy was removed in Drupal 10.… |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for templates previously inherited from the Classy theme. WHY WERE CLASSY TEMPLATES COPIED HERE? ------------------------------------------- Classy was removed in Drupal… |
| README.txt | file | core/ |
ABOUT STABLE 9 -------------- Stable 9 allows core markup and styling to evolve by functioning as a backwards compatibility layer for themes against changes to core markup and CSS. If you browse Stable 9's contents, you will find copies of all… |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for image files previously inherited from the Classy theme. WHY WERE CLASSY IMAGE FILES COPIED HERE? ------------------------------------------- Classy was removed in… |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for CSS files previously inherited from the Classy theme. WHY WERE CLASSY CSS FILES COPIED HERE? ------------------------------------------- Classy was removed in Drupal… |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for JS files previously inherited from the Classy theme. WHY WERE CLASSY JS FILES COPIED HERE? ------------------------------------------- Classy was removed in Drupal 10.… |
| README.txt | file | core/ |
WHAT IS THIS DIRECTORY FOR? -------------------------------- This directory is for templates previously inherited from the Classy theme. WHY WERE CLASSY TEMPLATES COPIED HERE? ------------------------------------------- Classy was removed in Drupal… |
| README.txt | file | core/ |
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 | core/ |
This folder contains tests of the update system. Tests of System module's hook_update_N() and hook_post_update_NAME() implementations should be placed in core/modules/system/tests/src/Functional/Update. |
| README.txt | file | core/ |
This folder contains tests of System module's hook_update_N() and hook_post_update_NAME() implementations. Tests of the update system should be placed in core/modules/system/tests/src/Functional/UpdateSystem. |
| README.txt | file | core/ |
The classes in this directory act as a mock plugin type to test annotated class discovery. See the corresponding test file: /core/modules/system/src/Tests/Plugin/Discovery/AnnotatedClassDiscoveryTest.php |
| README.txt | file | core/ |
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. |
| README.txt | file | core/ |
Drupal Scaffold Files are files that are contained inside drupal/core, but are installed outside of the core directory (e.g. at the Drupal root). For now, the scaffold files are being maintained in their original locations. This is done so that… |
| README.txt | file | core/ |
Drupal core uses the UMD build of tabbable. To create this build: Navigate to the root directory of the tabbable library. Ensure that dependencies have been installed: ``` yarn install ``` Build files for production: ``` yarn build ``` This will… |
| README.txt | file | core/ |
Code in the Drupal\Core namespace represents Drupal Subsystems provided by the base system. These subsystems MAY depend on Drupal Components and other Subsystems, but MAY NOT depend on any code in a module. Each Subsystem should be in its own… |
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.