- Issue created by @michelle
i have same issue, i'm still in D9, so the pages that have viewsreferences not working and displaying the same error, any help ?
- Status changed to Closed: won't fix
4 months ago 3:59am 26 August 2024 - 🇬🇧United Kingdom scott_euser
If you are locking into an older unsupported version of core it seems you'll also need to lock into an older version of this until you are ready to upgrade into supported versions of things.
Maybe modules like Drupal Rector and Upgrade Status can help with the updates.
I don't think it'd be normal for a module to have to say in composer or info yml that it's incompatible with something unless it's a supported version but I could be missing a doc page and could be wrong.
- 🇺🇸United States michelle Wisconsin, USA
At the time I wrote this, beta9 was the latest version and, as you can see → , it is listed as D9 compatible, which it is not. I wasn't expecting you to make it D9 compatible; I was just documenting the issue on the release page. Since that is no longer the latest version, and the D9 compatibility listing has been removed from the latest version, it's likely no longer an issue but you might want to consider fixing that release, anyway, just to avoid any issues for anyone still on D9.
- Status changed to Fixed
3 months ago 4:03pm 7 September 2024 - 🇬🇧United Kingdom scott_euser
Makes sense, thank you! We changed that in 📌 Remove mention of Drupal 9 support from info.yml file Fixed and just released it. I don't think we can go back and modify already tagged releases though unfortunately but I expect others locked to D9 will hit this issue so hopefully will then know what to do.
Automatically closed - issue fixed for 2 weeks with no activity.