Initial Drupal 11 with DDEV setup
This commit is contained in:
gluebox
20
web/core/modules/system/help_topics/system.cache.html.twig
Normal file
20
web/core/modules/system/help_topics/system.cache.html.twig
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
label: 'Clearing the site cache'
|
||||
related:
|
||||
- core.maintenance
|
||||
---
|
||||
{% set performance_link_text %}{% trans %}Performance{% endtrans %}{% endset %}
|
||||
{% set performance_link = render_var(help_route_link(performance_link_text, 'system.performance_settings')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Clear the data in the site cache.{% endtrans %}</p>
|
||||
<h2>{% trans %}What is the cache?{% endtrans %}</h2>
|
||||
<p>{% trans %}Some of the calculations that are done when your site loads a page take a long time to run. To save time when these calculations would need to be done again, their results can be <em>cached</em> in your site's database. There are internal mechanisms to <em>clear</em> cached data when the conditions or assumptions that went into the calculation have changed, but you can also clear cached data manually. When your site is misbehaving, a good first step is to clear the cache and see if the problem goes away.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>{{ performance_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Clear all caches</em>. Your site's cached data will be cleared.{% endtrans %}</li>
|
||||
</ol>
|
||||
<h2>{% trans %}Additional resources{% endtrans %}</h2>
|
||||
<ul>
|
||||
<li>{% trans %}<a href="https://www.drupal.org/docs/user_guide/en/prevent-cache.html">Concept: Cache (Drupal User Guide)</a>{% endtrans %}</li>
|
||||
</ul>
|
||||
@ -0,0 +1,30 @@
|
||||
---
|
||||
label: 'Changing basic site settings'
|
||||
top_level: true
|
||||
related:
|
||||
- user.security_account_settings
|
||||
---
|
||||
{% set regional_link_text %}{% trans %}Regional settings{% endtrans %}{% endset %}
|
||||
{% set regional_link = render_var(help_route_link(regional_link_text, 'system.regional_settings')) %}
|
||||
{% set information_link_text %}{% trans %}Basic site settings{% endtrans %}{% endset %}
|
||||
{% set information_link = render_var(help_route_link(information_link_text, 'system.site_information_settings')) %}
|
||||
{% set datetime_link_text %}{% trans %}Date and time formats{% endtrans %}{% endset %}
|
||||
{% set datetime_link = render_var(help_route_link(datetime_link_text, 'entity.date_format.collection')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Configure the basic settings of your site, including the site name, slogan, main email address, default time zone, default country, and the date formats to use.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>System</em> > <em>{{ information_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Enter the site name, slogan, and main email address for your site. {% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Save configuration</em>. You should see a message indicating that the settings were saved.{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Region and language</em> > <em>{{ regional_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Select the default country and default time zone for your site.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Save configuration</em>. You should see a message indicating that the settings were saved.{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Region and language</em> > <em>{{ datetime_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Look at the <em>Patterns</em> for the Default long, medium, and short date formats. If any of them does not match the date format you want to use on your site, click <em>Edit</em> in that row to edit the format.{% endtrans %}</li>
|
||||
<li>{% trans %}Adjust the <em>Format string</em> until the <em>Displayed</em> format matches what you want. (Date format strings are composed of PHP date format codes.){% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Save format</em>. You should see a message indicating that the format was saved.{% endtrans %}</li>
|
||||
<li>{% trans %}Repeat the previous three steps for any other date formats that need to be changed.{% endtrans %}</li>
|
||||
</ol>
|
||||
<h2>{% trans %}Additional resources{% endtrans %}</h2>
|
||||
<p>{% trans %}<a href="https://www.php.net/manual/datetime.format.php#refsect1-datetime.format-parameters">PHP date format codes reference</a>{% endtrans %}</p>
|
||||
@ -0,0 +1,26 @@
|
||||
---
|
||||
label: 'Configuring error responses, including 403/404 pages'
|
||||
related:
|
||||
- system.config_basic
|
||||
- core.maintenance
|
||||
---
|
||||
{% set log_settings_link_text %}{% trans %}Logging and errors{% endtrans %}{% endset %}
|
||||
{% set log_settings_link = render_var(help_route_link(log_settings_link_text, 'system.logging_settings')) %}
|
||||
{% set information_link_text %}{% trans %}Basic site settings{% endtrans %}{% endset %}
|
||||
{% set information_link = render_var(help_route_link(information_link_text, 'system.site_information_settings')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Set up your site to respond appropriately to site errors, including 403 and 404 page responses.{% endtrans %}</p>
|
||||
<h2>{% trans %}What are 403 and 404 responses?{% endtrans %}</h2>
|
||||
<p>{% trans %}When a user visits a web page, the web server sends a response code in addition to the page content. A normal, non-error response has code 200. If the page does not exist on the site, the response code is 404. If the page exists, but the user is not authorized to visit the page, the response code is 403. The core software provides default responses for both 403 and 404 codes, but if you prefer, you can create your own pages for each.{% endtrans %}</p>
|
||||
<h2>{% trans %}What other errors can occur?{% endtrans %}</h2>
|
||||
<p>{% trans %}Under some situations, your site can generate error messages. These can be due to user errors (such as entering invalid values in a form, or incorrect configuration), PHP runtime errors, or software bugs. Some errors may result in a <em>white screen of death</em> (a totally blank web page response); less drastic errors will generate error messages. You can configure what happens when an error message is generated.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps {% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}If desired, create pages to use for 403 and 404 responses. Note the URLs for these pages.{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>System</em> > <em>{{ information_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Error pages</em> section, enter the URL for your 403/404 pages, starting after the site home page URL. For example, if your site URL is <em>https://example.com</em> and your 404 page is <em>https://example.com/not-found</em>, you would enter <em>/not-found</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Save configuration</em>. You should see a message indicating that the settings were saved.{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>{{ log_settings_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}For a production site, select <em>None</em> under <em>Error messages to display</em>. For a site that is in development, select one of the other options, so that you are more aware of the errors the site is generating.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Save configuration</em>. You should see a message indicating that the settings were saved.{% endtrans %}</li>
|
||||
</ol>
|
||||
@ -0,0 +1,22 @@
|
||||
---
|
||||
label: 'Enabling and disabling maintenance mode'
|
||||
related:
|
||||
- core.maintenance
|
||||
- system.cache
|
||||
---
|
||||
{% set cache_topic = render_var(help_topic_link('system.cache')) %}
|
||||
{% set maintenance_link_text %}{% trans %}Maintenance mode{% endtrans %}{% endset %}
|
||||
{% set maintenance_link = render_var(help_route_link(maintenance_link_text, 'system.site_maintenance_mode')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Put your site in maintenance mode to perform maintenance operations, and then return to normal mode when finished.{% endtrans %}</p>
|
||||
<h2>{% trans %}What is maintenance mode?{% endtrans %}</h2>
|
||||
<p>{% trans %}When your site is in maintenance mode, most site visitors will see a simple maintenance mode message page, rather than being able to use the full functionality of the site. Users with <em>Use the site in maintenance mode</em> permission who are already logged in will be able to use the full site, and the log in page at <em>/user</em> will also be accessible to anyone.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>{{ maintenance_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Check <em>Put site into maintenance mode</em>, optionally change the <em>Message to display when in maintenance mode</em>, and click <em>Save configuration</em>. Your site will be in maintenance mode.{% endtrans %}</li>
|
||||
<li>{% trans %}Perform your maintenance operations.{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>{{ maintenance_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Uncheck <em>Put site into maintenance mode</em> and click <em>Save configuration</em>. Your site will be back in normal operation mode.{% endtrans %}</li>
|
||||
<li>{% trans %}Clear the site cache. See {{ cache_topic }} for instructions.{% endtrans %}</li>
|
||||
</ol>
|
||||
@ -0,0 +1,18 @@
|
||||
---
|
||||
label: 'Installing a module'
|
||||
related:
|
||||
- core.extending
|
||||
- system.module_uninstall
|
||||
---
|
||||
{% set extend_link_text %}{% trans %}Extend{% endtrans %}{% endset %}
|
||||
{% set extend_link = render_var(help_route_link(extend_link_text, 'system.modules_list')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Install a core module, or a contributed module that has already been downloaded.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>{{ extend_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Enter a word from the module name or description into the filter box, to make the list of modules smaller. Locate the module you want to install.{% endtrans %}</li>
|
||||
<li>{% trans %}Check the box next to the name of the module you want to install; you can also check more than one box to install multiple modules at the same time. If the checkbox is disabled for the module you are trying to install, expand the information to see why -- you may need to download an additional module that your module requires.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Install</em> at the bottom of the page. If you chose to install a module with dependencies that were not already installed, or if you chose an Experimental module, confirm your choice on the next page.{% endtrans %}</li>
|
||||
<li>{% trans %}Wait for the module (or modules) to be installed. You should be returned to the <em>Extend</em> page with a message saying the module or modules were installed.{% endtrans %}</li>
|
||||
</ol>
|
||||
@ -0,0 +1,21 @@
|
||||
---
|
||||
label: 'Uninstalling a module'
|
||||
related:
|
||||
- core.extending
|
||||
- system.module_install
|
||||
- system.maintenance_mode
|
||||
---
|
||||
{% set uninstall_link_text %}{% trans %}Uninstall{% endtrans %}{% endset %}
|
||||
{% set uninstall_link = render_var(help_route_link(uninstall_link_text, 'system.modules_uninstall')) %}
|
||||
{% set maintenance_topic = render_var(help_topic_link('system.maintenance_mode')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Uninstall a module. Your site should be in <em>maintenance mode</em> when you uninstall modules. See {{ maintenance_topic }} for details.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Extend</em> > <em>{{ uninstall_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Enter a word from the module name or description into the filter box, to make the list of modules smaller. Locate the module you want to uninstall.{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Description</em> column, see if there are reasons that this module cannot be uninstalled. For example, you may have created content using this module (which you would need to delete first), or there may be another module installed that requires this module to be installed (you would need to uninstall the other module first).{% endtrans %}</li>
|
||||
<li>{% trans %}If there are no reasons listed, the module can be uninstalled. Check the box in the <em>Uninstall</em> column, next to the module's name.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Uninstall</em> at the bottom of the page. Verify the list of modules to be uninstalled and configuration to be deleted on the confirmation page, and click <em>Uninstall</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Wait for the module to be uninstalled. You should be returned to the <em>Uninstall</em> page with a message saying the module was uninstalled.{% endtrans %}</li>
|
||||
</ol>
|
||||
21
web/core/modules/system/help_topics/system.reports.html.twig
Normal file
21
web/core/modules/system/help_topics/system.reports.html.twig
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
label: 'Running reports on your site'
|
||||
related:
|
||||
- core.maintenance
|
||||
- core.security
|
||||
- system.config_error
|
||||
---
|
||||
{% set status_link_text %}{% trans %}Status report{% endtrans %}{% endset %}
|
||||
{% set status_link = render_var(help_route_link(status_link_text, 'system.status')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Run reports to learn about the status and health of your site.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Reports</em> > <em>{{ status_link }}</em> to see a report that summarizes the health and status of your site. If there are any warnings or errors, you will need to fix them. Take note of any upcoming highly critical security releases that may impact your site.{% endtrans %}</li>
|
||||
<li>{% trans %}If you have the core Database Logging module installed, in the <em>Manage</em> administrative menu, navigate to <em>Reports</em> > <em>Recent log messages</em> to see a report of the error and informational messages your site has generated. You can filter the report by <em>Severity</em> to see only the most critical messages, if desired.{% endtrans %}</li>
|
||||
<li>{% trans %}If you have the core Update Status module installed, in the <em>Manage</em> administrative menu, navigate to <em>Reports</em> > <em>Available updates</em> to see a report of the updates that are available for your site software. If <em>Last checked</em> is far in the past, click <em>Check manually</em> to update the report. Scan the report; if the core software or any modules or themes have security updates available, you should update them as soon as possible.{% endtrans %}</li>
|
||||
</ol>
|
||||
<h2>{% trans %}Additional resources{% endtrans %}</h2>
|
||||
<ul>
|
||||
<li>{% trans %}<a href="https://www.drupal.org/docs/user_guide/en/security-chapter.html">Security and Maintenance (Drupal User Guide)</a>, which includes information on how to update your site's core software, modules, and themes.{% endtrans %}</li>
|
||||
</ul>
|
||||
@ -0,0 +1,19 @@
|
||||
---
|
||||
label: 'Installing a theme and setting default themes'
|
||||
related:
|
||||
- core.appearance
|
||||
- system.theme_uninstall
|
||||
---
|
||||
{% set themes_link_text %}{% trans %}Appearance{% endtrans %}{% endset %}
|
||||
{% set themes_link = render_var(help_route_link(themes_link_text, 'system.themes_page')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Install a core theme, or a contributed theme that has already been downloaded. Choose the default themes to use for the site and for administrative pages.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>{{ themes_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Locate the themes that you want to use as the site default theme and for administrative pages.{% endtrans %}</li>
|
||||
<li>{% trans %}For each of these themes, if the theme is in the <em>Uninstalled themes</em> section, click the <em>Install</em> link to install the theme. Wait for the theme to be installed (translations might be downloaded). You should be returned to the <em>Appearance</em> page.{% endtrans %}</li>
|
||||
<li>{% trans %}Locate the theme that you want to be your default theme, which should now be in the <em>Installed themes</em> section. If it is not already labeled as the <em>default theme</em>, click the <em>Set as default</em> link.{% endtrans %}</li>
|
||||
<li>{% trans %}At the bottom of the page, select the <em>Administration theme</em> that you want to use on administrative pages. Click <em>Save configuration</em> if you selected a new theme.{% endtrans %}</li>
|
||||
<li>{% trans %}If you changed the default theme for your site, visit the site home page or another page on the non-administration part of your site and verify that the site is using the new theme. If you changed the administration theme, verify that the new theme is used on administrative pages.{% endtrans %}</li>
|
||||
</ol>
|
||||
@ -0,0 +1,16 @@
|
||||
---
|
||||
label: 'Uninstalling an unused theme'
|
||||
related:
|
||||
- core.appearance
|
||||
- system.theme_install
|
||||
---
|
||||
{% set themes_link_text %}{% trans %}Appearance{% endtrans %}{% endset %}
|
||||
{% set themes_link = render_var(help_route_link(themes_link_text, 'system.themes_page')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Uninstall a theme that was previously installed, but is no longer being used on the site.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>{{ themes_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Locate the theme that you want to uninstall, in the <em>Installed themes</em> section.{% endtrans %}</li>
|
||||
<li>{% trans %}Click the <em>Uninstall</em> link to uninstall the theme. If there is not an <em>Uninstall</em> link, the theme cannot be uninstalled because it is either being used as the site default theme, being used as the <em>Administration theme</em>, or is the base theme for another installed theme.{% endtrans %}</li>
|
||||
</ol>
|
||||
Reference in New Issue
Block a user