- Issue created by @xeniksp
- Status changed to Needs review
over 1 year ago 2:26pm 30 May 2023 - last update
over 1 year ago 3 pass - Status changed to RTBC
over 1 year ago 10:46am 23 June 2023 - last update
over 1 year ago 3 pass - 🇧🇪Belgium bramvandenbulcke
Thanks for the patch! It's working as intended.
- First commit to issue fork.
- last update
about 1 year ago 3 pass - @parisek opened merge request.
- 🇨🇿Czech Republic parisek
xeniksp: Thank you for your patch, it fixed this issue, I created MR and hope that maintainer merge it soon.
- 🇬🇷Greece bserem
RTBC here too. I'm gonna bump this to critical, as the module is marked as D10 ready and there are production sites facing the issue after the upgrade.
Feel free to downgrade this back if I'm wrong here.
- 🇳🇱Netherlands watergate
I can confirm the patch applies cleanly on a Drupal 10.1 installation.
- Status changed to Needs work
about 1 year ago 9:01am 6 December 2023 - 🇧🇪Belgium weseze
I actually think the accessCheck should be FALSE here. I think it does not matter if the user deleting the translation has access to the paragraphs on the translation, they should be deleted anyway to prevent stale date in the database.
Setting back to needs work until I (or someone else) can confirm this.
- Status changed to Fixed
about 1 year ago 10:28am 8 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.