From 06df8f3c1988dad4d225bf416fa721ba712ce1c5 Mon Sep 17 00:00:00 2001 From: megakeegman Date: Fri, 28 Jan 2022 20:32:50 -0500 Subject: [PATCH] Commit drupal reformatting of config --- config/sync/tour.tour.honeypot.yml | 22 +++++++++---------- .../tour.tour.search-api-index-fields.yml | 20 ++++++++--------- .../sync/tour.tour.search-api-index-form.yml | 12 +++++----- .../tour.tour.search-api-index-processors.yml | 6 ++--- config/sync/tour.tour.search-api-index.yml | 22 +++++++++---------- .../sync/tour.tour.search-api-server-form.yml | 6 ++--- config/sync/tour.tour.search-api-server.yml | 8 +++---- config/sync/tour.tour.views-ui.yml | 22 +++++++++---------- 8 files changed, 59 insertions(+), 59 deletions(-) diff --git a/config/sync/tour.tour.honeypot.yml b/config/sync/tour.tour.honeypot.yml index 1b2852d..1a6910d 100644 --- a/config/sync/tour.tour.honeypot.yml +++ b/config/sync/tour.tour.honeypot.yml @@ -18,45 +18,45 @@ tips: plugin: text label: Honeypot weight: -10 - position: top-start body: "Congratulations on installing Honeypot on your site! With just a few clicks, you can have your site well-protected against automated spam bots.\r\n\r\nClick Next to be guided through this configuration page." + position: top-start protect-all-forms: id: protect-all-forms plugin: text label: 'Protect all forms' weight: -9 - position: bottom-start - selector: '#edit-protect-all-forms' body: "Protecting all the forms is the easiest way to quickly cut down on spam on your site, but doing this disables Drupal's caching for every page where a form is displayed.\r\n\r\nNote: If you have the honeypot time limit enabled, this option may cause issues with Drupal Commerce product forms or similarly-sparse forms that are able to be completed in a very short time." + selector: '#edit-protect-all-forms' + position: bottom-start log-blocked-form-submissions: id: log-blocked-form-submissions plugin: text label: 'Log blocked form submissions' weight: -8 - position: bottom-start - selector: '#edit-log' body: 'Check this box to log every form submission using watchdog. If you have Database Logging enabled, you can view these log entries in the Recent log messages page under Reports.' + selector: '#edit-log' + position: bottom-start honeypot-element-name: id: honeypot-element-name plugin: text label: 'Honeypot Element Name' weight: -7 - position: top-start - selector: '#edit-element-name' body: 'Spam bots typically fill out any field they believe will help get links back to their site, so tempting them with a field named something like ''url'', ''homepage'', or ''link'' makes it hard for them to resist filling in the field—and easy to catch them in the trap and reject their submissions!' + selector: '#edit-element-name' + position: top-start honeypot-time-limit: id: honeypot-time-limit plugin: text label: 'Honeypot Time Limit' weight: -6 - position: top-start - selector: '#edit-time-limit' body: 'If you enter a positive value, Honeypot will require that all protected forms take at least that many seconds long to fill out. Most forms take at least 5-10 seconds to complete (if you''re a human), so setting this to a value < 5 will help protect against spam bots. Set to 0 to disable.' + selector: '#edit-time-limit' + position: top-start honeypot-form-specific-settings: id: honeypot-form-specific-settings plugin: text label: 'Honeypot form-specific settings' weight: -5 - position: top-start - selector: '#edit-form-settings' body: 'If you would like to choose particular forms to be protected by Honeypot, check the forms you wish to protect in this section. Most common types of forms are available for protection.' + selector: '#edit-form-settings' + position: top-start diff --git a/config/sync/tour.tour.search-api-index-fields.yml b/config/sync/tour.tour.search-api-index-fields.yml index 1c286e8..f93635b 100644 --- a/config/sync/tour.tour.search-api-index-fields.yml +++ b/config/sync/tour.tour.search-api-index-fields.yml @@ -24,68 +24,68 @@ tips: plugin: text label: 'Add fields' weight: 2 - selector: '.button-action[data-drupal-selector="edit-add-field"]' body: 'With the "Add fields" button you can add additional fields to this index.' + selector: '.button-action[data-drupal-selector="edit-add-field"]' search-api-index-fields-label: id: search-api-index-fields-label plugin: text label: Label weight: 3 - selector: '.details-wrapper:nth(0) table thead th:nth(0)' body: 'A label for the field that will be used to refer to the field in most places in the user interface.' + selector: '.details-wrapper:nth(0) table thead th:nth(0)' search-api-index-fields-machine-name: id: search-api-index-fields-machine-name plugin: text label: 'Machine name' weight: 4 - selector: '.details-wrapper:nth(0) table thead th:nth(1)' body: 'The internal ID to use for this field. Can safely be ignored by inexperienced users in most cases. Changing a field''s machine name requires reindexing of the index.' + selector: '.details-wrapper:nth(0) table thead th:nth(1)' search-api-index-fields-property-path: id: search-api-index-fields-property-path plugin: text label: 'Property path' weight: 5 - selector: '.details-wrapper:nth(0) table thead th:nth(2)' body: 'The internal relationship linking the indexed item to the field, with links being separated by colons (:). This can be useful information for advanced users, but can otherwise be ignored.' + selector: '.details-wrapper:nth(0) table thead th:nth(2)' search-api-index-fields-type: id: search-api-index-fields-type plugin: text label: Type weight: 6 - selector: '.details-wrapper:nth(0) table thead th:nth(3)' body: 'The data type to use when indexing the field. Determines how a field can be used in searches. For information on the available types, see the "Data types" box at the bottom of the page.' + selector: '.details-wrapper:nth(0) table thead th:nth(3)' search-api-index-fields-boost: id: search-api-index-fields-boost plugin: text label: Boost weight: 7 - selector: '.details-wrapper:nth(0) table thead th:nth(4)' body: 'Only applicable for fulltext fields. Determines how "important" the field is compared to other fulltext fields, to influence scoring of fulltext searches.' + selector: '.details-wrapper:nth(0) table thead th:nth(4)' search-api-index-fields-edit: id: search-api-index-fields-edit plugin: text label: 'Edit field' weight: 8 - selector: '.details-wrapper:nth(0) table tbody td:nth(5) a' body: 'Some fields have additional configuration available, in which case an "Edit" link is displayed in the "Operations" column.' + selector: '.details-wrapper:nth(0) table tbody td:nth(5) a' search-api-index-fields-remove: id: search-api-index-fields-remove plugin: text label: 'Remove field' weight: 9 - selector: '.details-wrapper:nth(0) table tbody td:nth(6) a' body: 'Removes a field from the index again. (Note: Sometimes, a field is required (for example, by a processor) and cannot be removed.)' + selector: '.details-wrapper:nth(0) table tbody td:nth(6) a' search-api-index-fields-submit: id: search-api-index-fields-submit plugin: text label: 'Save changes' weight: 10 - selector: '#edit-actions-submit' body: 'This saves all changes made to the fields for this index. Until this button is pressed, all added, changed or removed fields will only be stored temporarily and not effect the actual index used in the rest of the site.' + selector: '#edit-actions-submit' search-api-index-fields-cancel: id: search-api-index-fields-cancel plugin: text label: 'Cancel changes' weight: 10 - selector: '#edit-actions-cancel' body: 'If you have made changes to the index''s fields but not yet saved them, the "Cancel" link lets you discard those changes.' + selector: '#edit-actions-cancel' diff --git a/config/sync/tour.tour.search-api-index-form.yml b/config/sync/tour.tour.search-api-index-form.yml index a348a15..d98bf30 100644 --- a/config/sync/tour.tour.search-api-index-form.yml +++ b/config/sync/tour.tour.search-api-index-form.yml @@ -26,40 +26,40 @@ tips: plugin: text label: 'Index name' weight: 2 - selector: '#edit-name' body: 'Enter a name to identify this index. For example, "Content index". This will only be displayed in the admin user interface.' + selector: '#edit-name' search-api-index-form-datasources: id: search-api-index-form-datasources plugin: text label: Datasources weight: 3 - selector: '#edit-datasources' body: 'Datasources define the types of items that will be indexed in this index. By default, all content entities (like content, comments and taxonomy terms) will be available here, but modules can also add their own.' + selector: '#edit-datasources' search-api-index-form-tracker: id: search-api-index-form-tracker plugin: text label: Tracker weight: 4 - selector: '#edit-tracker' body: 'An index''s tracker is the system that keeps track of which items there are available for the index, and which of them still need to be indexed. Changing the tracker of an existing index will lead to reindexing of all items.' + selector: '#edit-tracker' search-api-index-form-server: id: search-api-index-form-server plugin: text label: Server weight: 5 - selector: '#edit-server' body: 'The search server that the index should use for indexing and searching. If no server is selected here, the index cannot be enabled. An index can only have one server, but a server can have any number of indexes.' + selector: '#edit-server' search-api-index-form-description: id: search-api-index-form-description plugin: text label: 'Index description' weight: 6 - selector: '#edit-description' body: 'Optionally, enter a description to explain the function of the index in more detail. This will only be displayed in the admin user interface.' + selector: '#edit-description' search-api-index-form-options: id: search-api-index-form-options plugin: text label: 'Advanced options' weight: 7 - selector: '#edit-options' body: 'These options allow more detailed configuration of index behavior, but can usually safely be ignored by inexperienced users.' + selector: '#edit-options' diff --git a/config/sync/tour.tour.search-api-index-processors.yml b/config/sync/tour.tour.search-api-index-processors.yml index 61451d0..33562e0 100644 --- a/config/sync/tour.tour.search-api-index-processors.yml +++ b/config/sync/tour.tour.search-api-index-processors.yml @@ -24,19 +24,19 @@ tips: plugin: text label: 'Enable processors' weight: 2 - selector: '#edit-status' body: 'This lists all processors available for this index and lets you choose the ones that should be active. (Note: Some processors cannot be disabled.)' + selector: '#edit-status' search-api-index-processors-weights: id: search-api-index-processors-weights plugin: text label: 'Processor order' weight: 3 - selector: '#edit-weights' body: 'This shows you which enabled processors will be active in the different parts of the indexing/searching workflow, and lets you re-arrange them. This should usually not be necessary, and only be used by advanced users as some processors will lead to unexpected results when used in the wrong order.' + selector: '#edit-weights' search-api-index-processors-settings: id: search-api-index-processors-settings plugin: text label: 'Processor settings' weight: 4 - selector: .form-type-vertical-tabs body: 'Some processors have additional configuration available, which you are able to change here.' + selector: .form-type-vertical-tabs diff --git a/config/sync/tour.tour.search-api-index.yml b/config/sync/tour.tour.search-api-index.yml index b345fcb..0f8a7b5 100644 --- a/config/sync/tour.tour.search-api-index.yml +++ b/config/sync/tour.tour.search-api-index.yml @@ -24,75 +24,75 @@ tips: plugin: text label: 'Index status' weight: 2 - selector: .search-api-index-status body: 'This gives a summary about how many items are known for this index, and how many have been indexed in their latest version. Items that are not indexed yet cannot be found by searches.' + selector: .search-api-index-status search-api-index-status: id: search-api-index-status plugin: text label: Status weight: 3 - selector: .search-api-index-summary--status body: 'Shows whether the index is currently enabled or disabled.' + selector: .search-api-index-summary--status search-api-index-datasources: id: search-api-index-datasources plugin: text label: Datasources weight: 4 - selector: .search-api-index-summary--datasource body: 'Lists all datasources that are enabled for this index.' + selector: .search-api-index-summary--datasource search-api-index-tracker: id: search-api-index-tracker plugin: text label: Tracker weight: 5 - selector: .search-api-index-summary--tracker body: 'The tracker used by the index. Only one ("Default") is available by default.' + selector: .search-api-index-summary--tracker search-api-index-server: id: search-api-index-server plugin: text label: Server weight: 6 - selector: .search-api-index-summary--server body: 'If the index is attached to a server, this server is listed here.' + selector: .search-api-index-summary--server search-api-index-server-index-status: id: search-api-index-server-index-status plugin: text label: 'Server index status' weight: 7 - selector: .search-api-index-summary--server-index-status body: 'For enabled indexes, the number of items that can actually be retrieved from the server is listed here. For reasons why this number might differ from the number under "Index status", see the module''s documentation.' + selector: .search-api-index-summary--server-index-status search-api-index-cron-batch-size: id: search-api-index-cron-batch-size plugin: text label: 'Cron batch size' weight: 8 - selector: .search-api-index-summary--cron-batch-size body: 'The number of items that will be indexed at once during cron runs.' + selector: .search-api-index-summary--cron-batch-size search-api-index-index-now: id: search-api-index-remove plugin: text label: 'Start indexing now' weight: 9 - selector: '#edit-index' body: 'The "Start indexing now" form allows indexing items manually right away, with a batch process. Otherwise, items are only indexed during cron runs. The form might be disabled if indexing is currently not possible for some reason, or not necessary.' + selector: '#edit-index' search-api-index-tracking: id: search-api-index-tracking plugin: text label: 'Track items for index' weight: 10 - selector: '#edit-tracking' body: 'In certain situations, the index''s tracker doesn''t have the latest state of the items available for indexing. This will be automatically rectified during cron runs, but can also be manually triggered here, with the "Track now" button.' + selector: '#edit-tracking' search-api-index-reindex: id: search-api-index-reindex plugin: text label: 'Queue all items for reindexing' weight: 11 - selector: '#edit-reindex' body: 'This will queue all items on this index for reindexing. Previously indexed data will remain on the search server, so searches on this index will continue to yield results.' + selector: '#edit-reindex' search-api-index-clear: id: search-api-index-clear plugin: text label: 'Clear all indexed data' weight: 12 - selector: '#edit-clear' body: 'This will remove all indexed content for this index from the search server and queue it for reindexing. Searches on this index will not return any results until items are reindexed.' + selector: '#edit-clear' diff --git a/config/sync/tour.tour.search-api-server-form.yml b/config/sync/tour.tour.search-api-server-form.yml index 4af6d6c..90726b8 100644 --- a/config/sync/tour.tour.search-api-server-form.yml +++ b/config/sync/tour.tour.search-api-server-form.yml @@ -26,19 +26,19 @@ tips: plugin: text label: 'Server name' weight: 2 - selector: '#edit-name' body: 'Enter a name to identify this server. For example, "Solr server". This will only be displayed in the admin user interface.' + selector: '#edit-name' search-api-server-form-description: id: search-api-server-form-description plugin: text label: 'Server description' weight: 3 - selector: '#edit-description' body: 'Optionally, enter a description to explain the function of the server in more detail. This will only be displayed in the admin user interface.' + selector: '#edit-description' search-api-server-form-backend: id: search-api-server-form-backend plugin: text label: 'Server backend' weight: 4 - selector: '#edit-backend' body: 'Servers can be based on different technologies. These are called "backends". A server uses exactly one backend and cannot change it later. You can make the "Database" backend available by enabling the "Database Search" module. Another very common backend is "Solr", which requires to be set up separately.' + selector: '#edit-backend' diff --git a/config/sync/tour.tour.search-api-server.yml b/config/sync/tour.tour.search-api-server.yml index a765b7c..9be79b0 100644 --- a/config/sync/tour.tour.search-api-server.yml +++ b/config/sync/tour.tour.search-api-server.yml @@ -24,26 +24,26 @@ tips: plugin: text label: Status weight: 2 - selector: .search-api-server-summary--status body: 'Shows whether the server is currently enabled or disabled.' + selector: .search-api-server-summary--status search-api-server-backend: id: search-api-server-backend plugin: text label: 'Backend class' weight: 3 - selector: .search-api-server-summary--backend body: 'The backend plugin used for this server. The backend plugin determines how items are indexed and searched – for example, using the database or an Apache Solr server.' + selector: .search-api-server-summary--backend search-api-server-indexes: id: search-api-server-indexes plugin: text label: 'Search indexes' weight: 4 - selector: .search-api-server-summary--indexes body: 'Lists all search indexes that are attached to this server.' + selector: .search-api-server-summary--indexes search-api-server-clear: id: search-api-server-clear plugin: text label: 'Delete all indexed data' weight: 5 - selector: '#edit-clear' body: 'This will permanently remove all data currently indexed on this server for indexes that aren''t read-only. Items are queued for reindexing. Until reindexing occurs, searches for the affected indexes will not return any results.' + selector: '#edit-clear' diff --git a/config/sync/tour.tour.views-ui.yml b/config/sync/tour.tour.views-ui.yml index 4216b8b..79d793f 100644 --- a/config/sync/tour.tour.views-ui.yml +++ b/config/sync/tour.tour.views-ui.yml @@ -26,63 +26,63 @@ tips: plugin: text label: 'Displays in this view' weight: 2 - selector: '#views-display-top' body: 'A display is a way of outputting the results, e.g., as a page or a block. A view can contain multiple displays, which are listed here. The active display is highlighted.' + selector: '#views-display-top' views-ui-view-admin: id: views-ui-view-admin plugin: text label: 'View administration' weight: 3 - position: left-start - selector: '#views-display-extra-actions' body: 'Perform administrative tasks, including adding a description and creating a clone. Click the drop-down button to view the available options.' + selector: '#views-display-extra-actions' + position: left-start views-ui-format: id: views-ui-format plugin: text label: 'Output format' weight: 4 - selector: .views-ui-display-tab-bucket.format body: 'Choose how to output results. E.g., choose Content to output each item completely, using your configured display settings. Or choose Fields, which allows you to output only specific fields for each result. Additional formats can be added by installing modules to extend Drupal''s base functionality.' + selector: .views-ui-display-tab-bucket.format views-ui-fields: id: views-ui-fields plugin: text label: Fields weight: 5 - selector: .views-ui-display-tab-bucket.field body: 'If this view uses fields, they are listed here. You can click on a field to configure it.' + selector: .views-ui-display-tab-bucket.field views-ui-filter: id: views-ui-filter plugin: text label: 'Filter your view' weight: 6 - selector: .views-ui-display-tab-bucket.filter body: 'Add filters to limit the results in the output. E.g., to only show content that is published, you would add a filter for Published and select Yes.' + selector: .views-ui-display-tab-bucket.filter views-ui-filter-operations: id: views-ui-filter-operations plugin: text label: 'Filter actions' weight: 7 - selector: '.views-ui-display-tab-bucket.filter .dropbutton-widget' body: 'Add, rearrange or remove filters.' + selector: '.views-ui-display-tab-bucket.filter .dropbutton-widget' views-ui-sorts: id: views-ui-sorts plugin: text label: 'Sort Criteria' weight: 8 - selector: .views-ui-display-tab-bucket.sort body: 'Control the order in which the results are output. Click on an active sort rule to configure it.' + selector: .views-ui-display-tab-bucket.sort views-ui-sorts-operations: id: views-ui-sorts-operations plugin: text label: 'Sort actions' weight: 9 - selector: '.views-ui-display-tab-bucket.sort .dropbutton-widget' body: 'Add, rearrange or remove sorting rules.' + selector: '.views-ui-display-tab-bucket.sort .dropbutton-widget' views-ui-preview: id: views-ui-preview plugin: text label: Preview weight: 10 - position: left-start - selector: '#preview-submit' body: 'Show a preview of the view output.' + selector: '#preview-submit' + position: left-start