- Issue created by @Cheope
- First commit to issue fork.
- Status changed to Closed: won't fix
8 months ago 3:16pm 13 April 2024 - 🇬🇧United Kingdom adamps
The release note was deliberately vague because it's a security fix so we avoid making it too obvious how to exploit it. The previous behaviour was a bug, it should never have been like that. I understand that this caused inconvenience for you however it was pure chance that your site previously worked. By default unpublished nodes aren't accessible and this module (now correctly) doesn't change that.