Revert "Added case fee and case provision permissions to GNO admin user"

This reverts commit d86f4abe6f.

config/core.extension.yml

@@ -82,6 +82,8 @@ module:
   paragraphs: 11
   standard: 1000
 theme:
+  stable: 0
+  classy: 0
   bartik: 0
   seven: 0
 profile: standard

config/feeds.feed_type.cav_projects_2.yml

@@ -33,7 +33,6 @@ processor_configuration:
   skip_hash_check: false
   values:
     type: project
-  insert_new: 1
 custom_sources:
   client:
     label: CLIENT

config/feeds.feed_type.csv_fee_categories_and_fees.yml

@@ -32,7 +32,6 @@ processor_configuration:
   skip_hash_check: false
   values:
     type: project_fee
-  insert_new: 1
 custom_sources:
   fee_category:
     label: 'FEE CATEGORY'

config/feeds.feed_type.csv_projects.yml

@@ -29,6 +29,5 @@ processor_configuration:
   skip_hash_check: false
   values:
     type: article
-  insert_new: 1
 custom_sources: {  }
 mappings: {  }

config/feeds.feed_type.csv_training_entities.yml

@@ -35,7 +35,6 @@ processor_configuration:
   skip_hash_check: false
   values:
     type: training
-  insert_new: 1
 custom_sources:
   client:
     label: CLIENT

config/hal.settings.yml

@@ -1,3 +1,4 @@
 link_domain: null
+bc_file_uri_as_url_normalizer: false
 _core:
   default_config_hash: swYtdod4psGvRvRY6OTGagGJPAuknS7WMgn1089yjL0

config/rest.settings.yml

@@ -0,0 +1,3 @@
+bc_entity_resource_permissions: false
+_core:
+  default_config_hash: Jg3_yqsTIZ51KOKp3OV2KDVVrlx3N3OCEfniEse09KE

config/serialization.settings.yml

@@ -0,0 +1,4 @@
+bc_primitives_as_strings: false
+bc_timestamp_normalizer_unix: false
+_core:
+  default_config_hash: 6A1rmsmNf4SJrwCEt_aZyO_kPYuFnIOPC2n5lJiIftA

config/system.rss.yml

@@ -1,4 +1,8 @@
+channel:
+  description: ''
 items:
+  limit: 10
   view_mode: rss
+langcode: en
 _core:
   default_config_hash: TlH7NNk46phfxu1mSUfwg1C0YqaGsUCeD4l9JQnQlDU

config/tour.tour.search-api-index-fields.yml

@@ -25,67 +25,77 @@ tips:
     label: 'Add fields'
     body: 'With the "Add fields" button you can add additional fields to this index.'
     weight: 2
-    selector: '.button-action[data-drupal-selector="edit-add-field"]'
+    attributes:
+      data-class: 'button-action[data-drupal-selector="edit-add-field"]'
   search-api-index-fields-label:
     id: search-api-index-fields-label
     plugin: text
     label: Label
     body: 'A label for the field that will be used to refer to the field in most places in the user interface.'
     weight: 3
-    selector: '.details-wrapper:nth(0) table thead th:nth(0)'
+    attributes:
+      data-class: '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'
     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.'
     weight: 4
-    selector: '.details-wrapper:nth(0) table thead th:nth(1)'
+    attributes:
+      data-class: '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'
     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.'
     weight: 5
-    selector: '.details-wrapper:nth(0) table thead th:nth(2)'
+    attributes:
+      data-class: 'details-wrapper:nth(0) table thead th:nth(2)'
   search-api-index-fields-type:
     id: search-api-index-fields-type
     plugin: text
     label: Type
     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 <a href="#search-api-data-types-table">"Data types" box</a> at the bottom of the page.'
     weight: 6
-    selector: '.details-wrapper:nth(0) table thead th:nth(3)'
+    attributes:
+      data-class: 'details-wrapper:nth(0) table thead th:nth(3)'
   search-api-index-fields-boost:
     id: search-api-index-fields-boost
     plugin: text
     label: Boost
     body: 'Only applicable for fulltext fields. Determines how "important" the field is compared to other fulltext fields, to influence scoring of fulltext searches.'
     weight: 7
-    selector: '.details-wrapper:nth(0) table thead th:nth(4)'
+    attributes:
+      data-class: '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'
     body: 'Some fields have additional configuration available, in which case an "Edit" link is displayed in the "Operations" column.'
     weight: 8
-    selector: '.details-wrapper:nth(0) table tbody td:nth(5) a'
+    attributes:
+      data-class: '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'
     body: 'Removes a field from the index again. (Note: Sometimes, a field is required (for example, by a processor) and cannot be removed.)'
     weight: 9
-    selector: '.details-wrapper:nth(0) table tbody td:nth(6) a'
+    attributes:
+      data-class: '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'
     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.'
     weight: 10
-    selector: '#edit-actions-submit'
+    attributes:
+      data-id: edit-actions-submit
   search-api-index-fields-cancel:
     id: search-api-index-fields-cancel
     plugin: text
     label: 'Cancel changes'
     body: 'If you have made changes to the index''s fields but not yet saved them, the "Cancel" link lets you discard those changes.'
     weight: 10
-    selector: '#edit-actions-cancel'
+    attributes:
+      data-id: edit-actions-cancel

config/tour.tour.search-api-index-form.yml

@@ -27,39 +27,45 @@ tips:
     label: 'Index name'
     body: 'Enter a name to identify this index. For example, "Content index". This will only be displayed in the admin user interface.'
     weight: 2
-    selector: '#edit-name'
+    attributes:
+      data-id: edit-name
   search-api-index-form-datasources:
     id: search-api-index-form-datasources
     plugin: text
     label: 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.'
     weight: 3
-    selector: '#edit-datasources'
+    attributes:
+      data-id: edit-datasources
   search-api-index-form-tracker:
     id: search-api-index-form-tracker
     plugin: text
     label: 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.'
     weight: 4
-    selector: '#edit-tracker'
+    attributes:
+      data-id: edit-tracker
   search-api-index-form-server:
     id: search-api-index-form-server
     plugin: text
     label: 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.'
     weight: 5
-    selector: '#edit-server'
+    attributes:
+      data-id: edit-server
   search-api-index-form-description:
     id: search-api-index-form-description
     plugin: text
     label: 'Index 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.'
     weight: 6
-    selector: '#edit-description'
+    attributes:
+      data-id: edit-description
   search-api-index-form-options:
     id: search-api-index-form-options
     plugin: text
     label: 'Advanced options'
     body: 'These options allow more detailed configuration of index behavior, but can usually safely be ignored by inexperienced users.'
     weight: 7
-    selector: '#edit-options'
+    attributes:
+      data-id: edit-options

config/tour.tour.search-api-index-processors.yml

@@ -25,18 +25,21 @@ tips:
     label: 'Enable processors'
     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.)'
     weight: 2
-    selector: '#edit-status'
+    attributes:
+      data-id: edit-status
   search-api-index-processors-weights:
     id: search-api-index-processors-weights
     plugin: text
     label: 'Processor order'
     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.'
     weight: 3
-    selector: '#edit-weights'
+    attributes:
+      data-id: edit-weights
   search-api-index-processors-settings:
     id: search-api-index-processors-settings
     plugin: text
     label: 'Processor settings'
     body: 'Some processors have additional configuration available, which you are able to change here.'
     weight: 4
-    selector: .form-type-vertical-tabs
+    attributes:
+      data-class: form-type-vertical-tabs

config/tour.tour.search-api-index.yml

@@ -25,74 +25,85 @@ tips:
     label: '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.'
     weight: 2
-    selector: .search-api-index-status
+    attributes:
+      data-class: search-api-index-status
   search-api-index-status:
     id: search-api-index-status
     plugin: text
     label: Status
     body: 'Shows whether the index is currently enabled or disabled.'
     weight: 3
-    selector: .search-api-index-summary--status
+    attributes:
+      data-class: search-api-index-summary--status
   search-api-index-datasources:
     id: search-api-index-datasources
     plugin: text
     label: Datasources
     body: 'Lists all datasources that are enabled for this index.'
     weight: 4
-    selector: .search-api-index-summary--datasource
+    attributes:
+      data-class: search-api-index-summary--datasource
   search-api-index-tracker:
     id: search-api-index-tracker
     plugin: text
     label: Tracker
     body: 'The tracker used by the index. Only one ("Default") is available by default.'
     weight: 5
-    selector: .search-api-index-summary--tracker
+    attributes:
+      data-class: search-api-index-summary--tracker
   search-api-index-server:
     id: search-api-index-server
     plugin: text
     label: Server
     body: 'If the index is attached to a server, this server is listed here.'
     weight: 6
-    selector: .search-api-index-summary--server
+    attributes:
+      data-class: search-api-index-summary--server
   search-api-index-server-index-status:
     id: search-api-index-server-index-status
     plugin: text
     label: '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", <a href="https://www.drupal.org/docs/8/modules/search-api/getting-started/frequently-asked-questions#server-index-status">see the module''s documentation</a>.'
     weight: 7
-    selector: .search-api-index-summary--server-index-status
+    attributes:
+      data-class: 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'
     body: 'The number of items that will be indexed at once during cron runs.'
     weight: 8
-    selector: .search-api-index-summary--cron-batch-size
+    attributes:
+      data-class: search-api-index-summary--cron-batch-size
   search-api-index-index-now:
     id: search-api-index-remove
     plugin: text
     label: 'Start indexing now'
     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.'
     weight: 9
-    selector: '#edit-index'
+    attributes:
+      data-id: edit-index
   search-api-index-tracking:
     id: search-api-index-tracking
     plugin: text
     label: 'Track items for index'
     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.'
     weight: 10
-    selector: '#edit-tracking'
+    attributes:
+      data-id: edit-tracking
   search-api-index-reindex:
     id: search-api-index-reindex
     plugin: text
     label: 'Queue all items for reindexing'
     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.'
     weight: 11
-    selector: '#edit-reindex'
+    attributes:
+      data-id: edit-reindex
   search-api-index-clear:
     id: search-api-index-clear
     plugin: text
     label: 'Clear all indexed data'
     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.'
     weight: 12
-    selector: '#edit-clear'
+    attributes:
+      data-id: edit-clear

config/tour.tour.search-api-server-form.yml

@@ -27,18 +27,21 @@ tips:
     label: 'Server name'
     body: 'Enter a name to identify this server. For example, "Solr server". This will only be displayed in the admin user interface.'
     weight: 2
-    selector: '#edit-name'
+    attributes:
+      data-id: edit-name
   search-api-server-form-description:
     id: search-api-server-form-description
     plugin: text
     label: 'Server 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.'
     weight: 3
-    selector: '#edit-description'
+    attributes:
+      data-id: edit-description
   search-api-server-form-backend:
     id: search-api-server-form-backend
     plugin: text
     label: 'Server 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 <a href="https://www.drupal.org/project/search_api_solr">"Solr"</a>, which requires to be set up separately.'
     weight: 4
-    selector: '#edit-backend'
+    attributes:
+      data-id: edit-backend

config/tour.tour.search-api-server.yml

@@ -25,25 +25,29 @@ tips:
     label: Status
     body: 'Shows whether the server is currently enabled or disabled.'
     weight: 2
-    selector: .search-api-server-summary--status
+    attributes:
+      data-class: search-api-server-summary--status
   search-api-server-backend:
     id: search-api-server-backend
     plugin: text
     label: 'Backend class'
     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.'
     weight: 3
-    selector: .search-api-server-summary--backend
+    attributes:
+      data-class: search-api-server-summary--backend
   search-api-server-indexes:
     id: search-api-server-indexes
     plugin: text
     label: 'Search indexes'
     body: 'Lists all search indexes that are attached to this server.'
     weight: 4
-    selector: .search-api-server-summary--indexes
+    attributes:
+      data-class: search-api-server-summary--indexes
   search-api-server-clear:
     id: search-api-server-clear
     plugin: text
     label: 'Delete all indexed data'
     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.'
     weight: 5
-    selector: '#edit-clear'
+    attributes:
+      data-id: edit-clear

config/tour.tour.views-ui.yml

@@ -27,62 +27,71 @@ tips:
     label: 'Displays in this view'
     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.'
     weight: 2
-    selector: '#views-display-top'
+    attributes:
+      data-id: views-display-top
   views-ui-view-admin:
     id: views-ui-view-admin
     plugin: text
     label: 'View administration'
     body: 'Perform administrative tasks, including adding a description and creating a clone. Click the drop-down button to view the available options.'
     weight: 3
-    selector: '#views-display-extra-actions'
+    location: left
-    position: left-start
+    attributes:
+      data-id: views-display-extra-actions
   views-ui-format:
     id: views-ui-format
     plugin: text
     label: 'Output format'
     body: 'Choose how to output results. E.g., choose <em>Content</em> to output each item completely, using your configured display settings. Or choose <em>Fields</em>, which allows you to output only specific fields for each result. Additional formats can be added by installing modules to <em>extend</em> Drupal''s base functionality.'
     weight: 4
-    selector: .views-ui-display-tab-bucket.format
+    attributes:
+      data-class: views-ui-display-tab-bucket.format
   views-ui-fields:
     id: views-ui-fields
     plugin: text
     label: Fields
     body: 'If this view uses fields, they are listed here. You can click on a field to configure it.'
     weight: 5
-    selector: .views-ui-display-tab-bucket.field
+    attributes:
+      data-class: views-ui-display-tab-bucket.field
   views-ui-filter:
     id: views-ui-filter
     plugin: text
     label: 'Filter your view'
     body: 'Add filters to limit the results in the output. E.g., to only show content that is <em>published</em>, you would add a filter for <em>Published</em> and select <em>Yes</em>.'
     weight: 6
-    selector: .views-ui-display-tab-bucket.filter
+    attributes:
+      data-class: views-ui-display-tab-bucket.filter
   views-ui-filter-operations:
     id: views-ui-filter-operations
     plugin: text
     label: 'Filter actions'
     body: 'Add, rearrange or remove filters.'
     weight: 7
-    selector: '.views-ui-display-tab-bucket.filter .dropbutton-widget'
+    attributes:
+      data-class: 'views-ui-display-tab-bucket.filter .dropbutton-widget'
   views-ui-sorts:
     id: views-ui-sorts
     plugin: text
     label: 'Sort Criteria'
     body: 'Control the order in which the results are output. Click on an active sort rule to configure it.'
     weight: 8
-    selector: .views-ui-display-tab-bucket.sort
+    attributes:
+      data-class: views-ui-display-tab-bucket.sort
   views-ui-sorts-operations:
     id: views-ui-sorts-operations
     plugin: text
     label: 'Sort actions'
     body: 'Add, rearrange or remove sorting rules.'
     weight: 9
-    selector: '.views-ui-display-tab-bucket.sort .dropbutton-widget'
+    attributes:
+      data-class: 'views-ui-display-tab-bucket.sort .dropbutton-widget'
   views-ui-preview:
     id: views-ui-preview
     plugin: text
     label: Preview
     body: 'Show a preview of the view output.'
     weight: 10
-    selector: '#preview-submit'
+    location: left
-    position: left-start
+    attributes:
+      data-id: preview-submit

config/user.role.gno_admin_user.yml

@@ -7,33 +7,23 @@ label: 'GNO Additional Admin Permissions'
 weight: 4
 is_admin: null
 permissions:
-  - '9 edit any entities'
-  - 'add case fee entities'
-  - 'add case provision entities'
   - 'add equal opps entities'
   - 'administer users'
   - 'delete activity entities'
   - 'delete all trainer revisions'
   - 'delete bank account entities'
   - 'delete case entities'
-  - 'delete case fee entities'
-  - 'delete case provision entities'
   - 'delete equal opps entities'
   - 'delete event entities'
   - 'delete organisation entities'
   - 'delete trainer entities'
-  - 'edit case provision entities'
   - 'edit equal opps entities'
   - 'view edit delete all actor entities'
-  - 'view published case fee entities'
-  - 'view published case provision entities'
   - 'view published equal opps entities'
   - 'view unpublished activity entities'
   - 'view unpublished actor entities'
   - 'view unpublished bank account entities'
   - 'view unpublished case entities'
-  - 'view unpublished case fee entities'
-  - 'view unpublished case provision entities'
   - 'view unpublished equal opps entities'
   - 'view unpublished event entities'
   - 'view unpublished organisation entities'

config/views.settings.yml

@@ -5,13 +5,13 @@ ui:
   show:
     additional_queries: false
     advanced_column: false
+    master_display: false
     performance_statistics: false
     preview_information: true
     sql_query:
       enabled: false
       where: above
     display_embed: false
-    default_display: false
   always_live_preview: true
   exposed_filter_any_label: old_any
 field_rewrite_elements: