[From the developer I am working with, Carole:]<\/p>\n
I followed https:\/\/tri.be\/change-required-fields-on-community-event-submission-page\/ and added a filter to specify additional required fields on the community\/add (and edit) page. When I add ‘organizer’ to the array of required fields, changes made to the organizer of an event aren’t saved. As near as I can tell, here’s the basic repro:<\/p>\n
1. Add events via the community plugin (I’m signed in as an admin so they’re listed under My Events). Include an organizer (or choose an existing one).
\n2. Add a filter for tribe_events_community_required_fields that includes ‘organizer’. I also included ‘post_content’ and ‘post_title’
\n3. Edit an event via the plugin. Change the organizer to another value.
\n4. Save the event.
\n5. When taken to My Events page, click the Edit link for the event you just changed.
\nOBSERVED RESULTS: The organizer is still the original value,
\nEXPECTED RESULTS: The organizer is changed to the value entered in step 3.
\n6. Remove the filter in step 2 or just remove ‘organizer’ from the array
\n7. Repeat steps 3-5
\nOBSERVED RESULTS: The organizer has been changed to the new value.<\/p>\n
After finding https:\/\/theeventscalendar.com\/support\/forums\/topic\/required-fields-in-community-events\/ and https:\/\/theeventscalendar.com\/support\/forums\/topic\/change-required-fields-on-community-event-submission-page\/, I took a closer look at the tutorial. While the tutorial sort of warns about using indexes in fields, it doesn’t warn about using ‘venue’ and ‘organizer’. If no more information can be added about making these fields required, those values should be removed from the list of Possible Field Names to Include, as including them introduces a bug. <\/p>\n
Ideally, the tutorial would show, or at least hint, at what’s needed to make organizer and venue required. Can I return an array of an array, ie., return array(‘organizer’, array(‘Organizer’)) to require the Organizer[Organizer] field? Upon closer inspection, I see that I’d still have to account for the id being selected or all the fields having values. At that point, it seems that JavaScript is probably better than using the filter. OK, yeah I get why the tutorial stops short of that.<\/p>\n
But I still contend that the tutorial implies one should add ‘organizer’ in the filter, but doing so results in breaking behavior. And that needs to be addressed.<\/p>\n","protected":false},"template":"","class_list":["post-179414","topic","type-topic","status-closed","hentry"],"yoast_head":"\n