- Issue created by @KlemenDEV
- Status changed to Postponed: needs info
over 1 year ago 12:55pm 11 July 2023 - 🇺🇸United States robphillips
What are your permission settings? What are your comment delete settings? Please provide specific steps to replicate.
- 🇸🇮Slovenia KlemenDEV
I use the "hard delete" option. Permission to hard delete is given to authenticated user roles for the desired content type, as well as "Delete own comments" permission.
On content type configuration, only hard delete is allowed, operation visibility is "Visible when multiple operations are available", default labels and 60 seconds for the "Delete time limit" which is enabled
- 🇺🇸United States robphillips
Would you mind providing a screenshot of both the comment delete and permissions table configurations? Or a configuration export.
- 🇸🇮Slovenia KlemenDEV
Attached is the content type config.
Authenticated user has the following permissions (I can't screenshot this page due to confidentiality):
* "Content: Allow (content type) Comments hard delete"
* "Delete own comments" - 🇺🇸United States robphillips
Thanks. The role that's having issues only has permissions to hard delete, correct? Also you have the delete time limit option enabled and set to 60 seconds. Are you testing as that role on a comment that has been created less than 60 seconds from it's creation?
- 🇸🇮Slovenia KlemenDEV
Are you testing as that role on a comment that has been created less than 60 seconds ago?
Yes, it is done in 60 seconds timeframe. The testing also goes well if the module version is reverted (same config and same test procedure).
- Assigned to robphillips
- Status changed to Active
over 1 year ago 4:12pm 19 July 2023 - 🇺🇸United States robphillips
Confirmed. Regression introduced in 🐛 Call to undefined method BaseFieldDefinition::getThirdPartySettings() Fixed .
- 4141b4e5 committed on 2.x
Issue #3373895: Fixes access regression introduced in #3336542
- 4141b4e5 committed on 2.x
- Status changed to Fixed
over 1 year ago 4:24pm 19 July 2023 - 🇸🇮Slovenia KlemenDEV
Neat, thank you for taking a look into this and fixing it :)
Automatically closed - issue fixed for 2 weeks with no activity.