-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Critical error when date fields are set but weekdays are not selected on drafts #22
Comments
Hi @Dasha1996, I am not able to reproduce.
What version of ACF RRule and Wordpress are you using? Also could you please provide the error message you got? |
Hi @marcbelletre, Were you saving/publishing the live post? It works fine when it is either publish or update a live post or page. Issue occurs only when working with drafts. My steps were:
I am using the latest version of the RRule plugin (1.3.11) and the latest version of ACF fields (6.2.2), my WordPress is also up to date - 6.3.2 I can do a screen recording if it helps? |
I did try saving a new post as draft. Could you please activate debugging (set |
yes sure, I will do it now |
That's the error I am getting
|
@Dasha1996 I just released v1.3.2 that fixes this issue. I managed to reproduce the error using the classic editor plugin. For some reason I didn't get the fatal error with the block editor. The quick fix was to exit before generating the RRule string when required arguments are missing. In this case the post will be saved successfully but the RRule field will be reset. |
@marcbelletre, that's strange that there is no error when using block editor, but there is when using classic editor. thank you so much for the fix! I tested it on staging - it works |
HI! Thank you so much for the plugin!
I just faced a small issue.
When the recurrence is set to weekly for example, but weekdays are not selected, on post save/update (only for drafts, published post update seems to be ok) it displays a critical error.
Is there a way to show a warning instead? None of my clients is technical so they sometimes forget by accident to set the occurrence and end up with a critical error when saving a post
The text was updated successfully, but these errors were encountered: