- Issue created by @rahul1707
- 🇳🇿New Zealand quietone
If this problem was discovered on a version of Drupal that is not 11.x, add that information in the issue summary and leave the version at 11.x. In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Also mentioned on the version → section of the list of issue fields documentation.
Un-assigning per Assigning ownership of a Drupal core issue → .
And +1 to #3. The standard issue template should be restored and as many sections as possible completed.
- 🇺🇸United States nicxvan
@rahul17 can you add the full issue template back and add some steps to reproduce?
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
This sounds like you have a record in your node table with a node type that no longer exists
- Issue was unassigned.
- Status changed to Closed: cannot reproduce
7 days ago 5:16am 9 September 2025 - 🇦🇺Australia acbramley
Closing this out as it's been >3 months since this was moved to PMNMI.
If you're still experiencing these issues, feel free to reopen this issue with more details on how to reproduce this. Thanks!
Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.
