- Issue created by @catapipper
- First commit to issue fork.
- @mandclu opened merge request.
- Status changed to Needs review
over 1 year ago 11:32am 11 May 2023 - π¨π¦Canada mandclu
Thanks for identifying this. It looks the the access check was needed in SmartDateRemoveInstanceForm.php. Please confirm that this resolves the problem for you as well.
- Status changed to RTBC
over 1 year ago 1:32pm 11 May 2023 -
mandclu β
committed 218418ae on 4.0.x
Issue #3359407 by mandclu: Cannot remove recurring instance
-
mandclu β
committed 218418ae on 4.0.x
- Status changed to Fixed
over 1 year ago 9:46am 13 May 2023 Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
over 1 year ago 5:35pm 30 June 2023 - πΈπͺSweden carolalind Nybro
I'm getting an error still on my site when trying to remove recurring instances. The error is "The was a problem with your form submission" but it doesn't happen with the admin role, only with the editor role.
I have granted access for editor on these :
- Cancel Smart Date Recur instances,
- Make Smart Dates recur,
- Reschedule Smart Date Recur instances.
What am I missing?
When I inspect with console it shows an ajax error.
- π¨π¦Canada mandclu
@carolalind were any errors logged? It sounds like it should be something permissions-related.
- πΈπͺSweden carolalind Nybro
@mandclu no nothing in the log at all. When I'm logged in as editor and click remove instance the text is not crossed over and if i try to save the node the error "There was a problem with your form submission" shows up. The node itself is registered in log as updated but the date isn't removed.
I also think it might be something related to permissions, but I can't figure out what. Everything connected to smart date and the booking nodetype have permissions correctly set as far as i can see.
It would be easier to locate if there was something logged when this happens.
Feeling a little lost here on how to proceed.
- πΈπͺSweden carolalind Nybro
@mandclu now I've checked every permission there is on my site and I finally found the one that broke the manage instances function. If I check the "Bypass Honeypot protection" permission for the editor role it works as designed. Must be a Honeypot problem then I guess???
Giving the severity of the bug, I believe this patch should probably be added to 3.7.x or 3.7.x be deprecated.