- Issue created by @mlncn
- 🇬🇧United Kingdom catch
Version shouldn't be required for custom profiles so we should be just not be rendering anything for it if it's not there.
Bumping to critical on the basis there must be a lot of versionless custom profiles out there.
- 🇦🇺Australia kim.pepper 🏄♂️🇦🇺Sydney, Australia
kim.pepper → made their first commit to this issue’s fork.
ronbot → changed the visibility of the branch 3511868-a-profile-without to hidden.
ronbot → changed the visibility of the branch 3511868-a-profile-without to active.
- 🇦🇺Australia kim.pepper 🏄♂️🇦🇺Sydney, Australia
We looked at this at the first-time contributor workshop at DrupalSouth 2025. The following users helped test this manually but could not reproduce:
atowl, lan, yi_jiang, Ronbot, nterbogt, silverham, tarawij, ben_a, cordo1, jimmycann, tyrellblackburn,
We tested by:
1. Deleting the version from the standard.info.yml file (which we installed)
2. Clearing our cache
3. Visiting the Status Report pageCan you please provide more steps to reproduce.
- 🇺🇸United States dcam
I just got bitten by this after upgrading a D10 site to D11 for the first time ever.
Hello new contributors at DrupalSouth! Here's some guidance for you:
You're right that this can't be reproduced with the Standard profile! The status report page specifically excludes the code that causes the bug when you're on the Standard profile. See the relevant line of code. You can reproduce this with any other profile. Try deleting the version from the Minimal profile instead!I've updated the issue summary with new instructions.