Hm, we don't have a component for the Standard install profile that I can see.
Problem/Motivation
If you install with the Standard install profile, you end up with config in your active config that does not match what is in the config/install files.
This is not a huge problem, but it does mean that if you use something like the Updates Report from this currently contrib/sandbox module: https://www.drupal.org/sandbox/jhodgdon/2391835 you will get a lot of false positives.
There are three sections to this report:
a) Config that is in a config/install of an active profile, theme, or module (extension) that is not in your site config.
b) Config that is in your active config that did not come from a config/install file.
c) Config that is in your active config that differs from the version in the config/install file. Note that this module, when it decides something "differs", it is ignoring:
- The order of config array elements at the top level and sub-levels of the config.
- Any 'uuid' elements.
- Any 'dependencies' sections. The reason I ignored these is that I think some of these are calculated by config entities and I was getting a lot of "diff" reports. Probably they shouldn't be ignored though? Not sure, but anyway this list ignores dependencies that are different from config/install to the active config.
Here is a list of config items that fall into one of these categories:
a) Missing config that should have been imported into active but wasn't:
block.block.bartik_search -- I filed this as a separate issue because it has actual UI implications: #2394423: Search block not being enabled in standard profile
b) Config that was added somehow in the install process but isn't in config/install:
1. Actions that are created when you add a role:
system.action.user_add_role_action.adminisrator
system.action.user_add_role_action.administrator
2. Block config that is created when you enable a theme:
block.block.classy_account_menu (and other classy blocks)
These are not bugs, I think. Just noting that they are there.
c) Config that differs:
1. Items that look like they need to be re-exported since config schema was changed:
block.block.bartik_account_menu (and most other blocks)
block_content.type.basic
core.entity_form_display.user.user.default
core.entity_view_display.user.user.compact
core.entity_view_display.user.user.default
field.field.node.article.field_image
field.field.node.article.field_tags
field.field.user.user.user_picture
field.storage.node.field_image
field.storage.node.field_tags
field.storage.user.user_picture
core.entity_form_mode.user.register
image.style.large
image.style.medium
image.style.thumbnail
system.menu.account
system.menu.admin
system.menu.footer
system.menu.main
system.menu.tools
rdf.mapping.node.article
rdf.mapping.node.page
rdf.mapping.taxonomy_term.tags
rdf.mapping.user.user
shortcut.set.default
filter.format.basic_html
filter.format.full_html
filter.format.plain_text
filter.format.restricted_html
tour.tour.views-ui
core.entity_view_mode.block_content.full (and all the other view modes)
All of these are missing components (like status, langcode, cache, etc.) that were probably added to the config after the last export, and I think these should be re-exported. One exception: the filter.format config in config/install has *additional* components (roles) that are missing in the active config (presumably that was removed from filter format config schema?). [BUG]
2. Contact form
contact.form.feedback - missing "recipient" but that is probably not a bug, since it's set to my sitewide email address. Yeah, that's done in standard_form_install_configure_submit(), it looks like.
3. Role
user.role.administrator (and the other roles) - config/install version is missing permissions. Not sure what that's about, but probably the standard install profile is adding the permissions in an install task? Let's see. Yes, standard_install() does add permissions. So I think this is not a bug.
Proposed resolution
a. File an issue about the search block. It isn't being enabled in the standard profile and should be.
b. I don't think these are problems.
c. Re-export the config items whose schema has changed.
Remaining tasks
Make a patch for (c) here.
User interface changes
None.
API changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | compare.txt | 22.24 KB | quietone |
Comments
Comment #9
quietone commentedUsing a standard install of Drupal 9.3.x.
1. Search is installed with standard profile, it is in the .info.yml
2. There was nothing to do here.
3.
git log --name-status -10 core/profiles/standard/config/install/shows that there have been quite a lot of changes to the config files for standard, I doubt there is a problem. Nonetheless, diddrush -y cexand wrote a script to do a diff on all the files in core/profiles/standard/config/install. The only differences were to things updated because of the install, like my username not admin and all the permissions in user.role.content_editor.yml. The latter is simply an indentation problem and I will make an issue for that, #3221206: Fix indentation in user.role.content_editor.yml.I don't see anything further to do here. Closing as outdated.
If that is wrong, reopen the issue, by setting the status to 'Active', and add a comment.
Thx
Comment #10
quietone commentedMeant to upload the results of the diff, if any one wants to check.