Submission Form – Required Fields and Error Message
I’ll be happy to help you with this issue.
I will run some tests on my end with those customizations and will come back to you to answer each of your questions.
My apologies for the delay here as we’ve been dealing with a higher demand in our forums this last couple of days.
Please hang in there.
Thanks again for your patience. Let me go through each of your questions:
1. The event description is required by the Community Submission form by default. If you want to not make it required, you can remove the post_content field from the required array by adding the following in the my_community_required_fields function:
unset( $fields );
2. EventStartHour and EventStartMinute are not valid fields to be required. Instead, you should use the EventStartTime value to require the Start Time.
3. Unfortunately, this is actually a bug we are already aware of. So I will link this thread to the bug report so we can let you know once a fix is released for it.
4. This is because you are adding the organizer to the required event fields in the ‘tribe_events_community_required_fields’ filter. This means that if the user does not create a new oganizer, it will be required to select one of the available.
Regarding the other code, I did a few tests with it and I could not find any issues about it. However, I would suggest you make a few tests with your own site (preferably in a staging/dev environment) to make sure that no conflicts arise before implementing in the live site.
I hope that helps. Let me know if you have any follow up questions and I’ll be happy to help.
Good morning Victor,
Thanks again for your advice and solutions. I’m happy to report that I was able to get the above issues fixed with the information you provided!
I’ll keep an eye out for a fix being released for the Date & Time bug.
Can you please confirm if #5 above (Venue and Organizer field values not being retained when an error is returned) will also be fixed when the fix is released for the Date & Time bug?
Lastly, the Additional Field values are not retained when an error message is returned. If that isn’t already in the above bug report, would you be able to verify and add those fields to the fix?
Thanks for following up with this. Happy to know you could solve the issues.
I’m sorry I missed point number five. This is different from the Date & Time bug, but I could reproduce and have already logged it as well. I’m not sure they will be fixed in the same release, as it might involve additional changes in how the fix is being applied. Nevertheless, we will keep you posted for both issues.
I have also added the additional fields not being retained issue to the bug logs. I have also linked them all together so they can hopefully be addressed at the same time as they are closely related and would be great to have them fixed in one maintenance release.
We appreciate you taking the time to report these issues.