- Issue created by @tstermitz
What exactly the Upgrade status says? is it your Sub-theme or Radix theme itself?
- π«π·France quimic Paris
I have the same issue. Upgrade status report Radix itself (not the sub-theme) as being incompatible.
- πΊπΈUnited States tstermitz Colorado
The incompatibility refers to Radix, not my subtheme. On some of the earlier RC releases, my subtheme also failed, but I was able to correct things - probably by re-writing the components correctly per the new way.
These are the Upgrade Status results:
Radix (radix) Contributed theme Installed 6.0.0-rc6 Local 11-Ready: Incompatible Drupal.org 11-Ready: Compatible
- Status changed to Postponed: needs info
2 days ago 2:59pm 6 January 2025 - πΊπΈUnited States DanChadwick
Looking at rc6, both the radix.info.yml and the starterkit info.yml indicate that radix v6 is compatible with D11.
I think upgrade status just considers the info.yml files. Is there some other issue, or can this be closed?
- π«π·France quimic Paris
@danchadwick Manually changing the
core_version_requirement
value in the sub-theme .info.yml file, to match that of Radix fixed the issue. Now Radix appears as compatible in the Upgrade Status module dashboard. I guess it means that this is an Upgrade Status module issue rather than a Radix issue. - πΊπΈUnited States tstermitz Colorado
Takig quimic's suggestion, I changed a couple lines in my subtheme.info.yml file, and that fixed the problem:
Change this to that:
core_version_requirement: ^10
core_version_requirement: ^10.3 || ^11For good measure, I also changed this to that:
version: 1.0.0
version: '6.0.0-rc6'And this to that:
generator: 'radix_starterkit:6.0.0-rc5'
generator: 'radix_starterkit:6.0.0-rc6'The first one was the one that actually did the trick.
- πΊπΈUnited States DanChadwick
@tstermitz: Yes, the core requirement in your subtheme matters. The version doesn't matter to drupal, so you can set it to whatever you want to track its version (which should not directly track radix, since your changes are different from radix's changes).
However, you might NOT want to update your starterkit version. You can use this to compare the templates (and maybe other files) between, say, rc5 and 6.0.0 stable to see what things were fixed in the starterkit templates that you might want to backport to your subtheme.
Without researching this, I'm guessing the core requirement was updated to include D11 between rc5 and rc6.
I'm closing this issue. If someone discovers an actual incompatibility with Drupal 11, please do open a new issue.