Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
This error is produced by Upgrade Status:
web/profiles/cappuccino/config/sync/core.base_field_override.block_content.basic.info.yml
Add core_version_requirement: ^8 || ^9 to profiles/cappuccino/config/sync/core.base_field_override.block_content.basic.info.yml to designate that the module is compatible with Drupal 9. See https://drupal.org/node/3070687.
The problem here is the following.
- One of the things Upgrade Status does is it checks info.yml files for core_version_requirement keys.
- This used to be done only to the root info.yml file of the project, but since #3132387: Subextension info.yml files not checked during module scan it is found everywhere under a project (except tests).
- As @mr.york points out, this becomes a problem when you have configuration yml files in your project which may also end up being named something.info.yml.
Proposed resolution
Avoid identifying info.yml files as extension definitions when a .yml file has more dots in it. This way we can ensure that a /config/ subdirectory is not ruled out for placing subextensions.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#13 | 3145821.patch | 909 bytes | Gábor Hojtsy |
#8 | interdiff_4-8.txt | 6.57 KB | ankitsingh0188 |
#8 | 3145821-8.patch | 8.93 KB | ankitsingh0188 |
#4 | Screenshot 2020-06-05 at 12.39.34 PM.png | 190.54 KB | ankitsingh0188 |
#4 | Screenshot 2020-06-05 at 1.03.47 PM.png | 16.06 KB | ankitsingh0188 |
Comments
Comment #2
Gábor HojtsyThanks for the report. Retitled for accuracy.
Comment #3
ankitsingh0188Comment #4
ankitsingh0188Created the patch with the latest code of the module. The module is now compatible with the drupal version 9.
No deprecations found.
Comment #6
ankitsingh0188Working on the test case failures.
Comment #7
ankitsingh0188Comment #8
ankitsingh0188Comment #9
ankitsingh0188Comment #10
Gábor Hojtsy@ankit.singh: two questions:
1. How are your patches related to this issue? The issue is about info.yml file detection being wrong.
2. Why are you "fixing" errors that we need to be present in the module to test for them. Upgrade Status is about finding those issues and we need files with issues to test with. We should not "fix" them.
Comment #11
ankitsingh0188@gábor-hojtsy
I think some confusion is there. Please brief me on what to do next here.
Comment #12
Gábor HojtsyUpdated the issue summary with what happens and what I think should be done to fix it.
Comment #13
Gábor HojtsyThis is a workable solution most likely.
Comment #15
Gábor HojtsyLet's go!