Can't save new calendar events after upgrade from Craft 4 to 5

[brandonjjon]

What happened?

It wants me to save the event first before adding pageHeader and pageContent but I can't save the event due to the validation errors. Definitely related to the new nesting stuff in Craft 5 but not sure what the best solve is here. pageHeader is a supertable and contentPage is a matrix. I have ran the console commands as well, fix-titles/fix-content etc. Can't really make these fields optional because they're used elsewhere. I can make Page Content optional in this calendar event entry type, but still doesn't fix the Page Header issue, would rather not make the minimum 0 on that one just to fix this. Any suggestions?

How can we reproduce this?

I'm not sure the exact steps to be honest.

1. Start on the latest version of Craft 4
2. Make sure you have a supertable field and a matrix field on your calendar event entry type
3. Make sure that works ok
4. Upgrade to Craft 5
5. Test creating an event after the upgrade

Calendar Edition

Pro

Calendar Version

5.0.21

Craft Version

5.8.12

When did this issue start?

• Unsure
• Fresh install of Calendar
• After upgrading from older Calendar version
• After upgrading from older Craft version
• After a change to hosting configuration

Previous Calendar Version

5.0.19

[kjmartens]

Sorry about this @brandonjjon, but it's a current limitation of Calendar in Craft 5.

We do have plans in the future to rewrite many parts of Calendar that will make it play nicer with Craft features. 🙂

[brandonjjon]

Hey @kjmartens appreciate the update. Any idea when we could expect an update there or any sort of workaround you could suggest in the meantime?

[brandonjjon]

Found a bit of a workaround for now. Allows saving the entry with just a title, then validation works as normal after that.

[kjmartens]

Thanks for sharing this @brandonjjon. We'll review this. 🙂

[seandelaney]

@kjmartens

v6 doesn't fix this issue.

If the Matrix field requires minimum 1 entry and the SuperTable field is a required field in the Calendar layout, then those requirements must be meet first. In v6 the user can save as Draft first so not sure if this is a workaround. I'd need to see the Matrix and SuperTable Entry Types to confirm.

IMO, this is not a Calendar issue. Its a field setup issue. If you add the same fields to a Single/Channel/Structure Entry Type layout and attempt to create a new Entry without the minimum Matrix entry or an empty SuperTable entry, you get the same errors:

I think the user needs to continue using Elements::EVENT_BEFORE_SAVE_ELEMENT as per the snippet above.