Venue name and City are required after update….when they're in the Saved Venue

[Mad Dog]

Thanks….we’re closer!

Once I fixed the misspelling of venue (whoops!) it works for the Venue and Organizer name. Now can we add “venue city” as a required field? I tried several variations (e.g., $fields[] = 'venue city';) but it keeps giving a validation error even if Venue City is filled in. Is there another way to specify that field?

We’re almost there!

[George]

Hey @mad dog,

Unfortunately specifying the venue city sub-field at this time is not possible 🙁

[Mad Dog]

Ah…now we’re getting down to it. Thanks for hanging in and checking.

Is Organizer Email available? That seemed to work before.

[George]

Hey @Mad Dog,

I’m sorry to continue to bear bad news, but I’ve tried for almost more than a half hour now and cannot get the Organizer Email field to work for this – it indeed did work in the past, but I think our new “multiple organizers” features in The Events Calendar core (which is where Community Events gets its core code from) has broken this ability to require “sub-fields” like Organizer Email or Venue City.

I’m really sorry about this, but if there’s any good news here is that’s your thread has brought this up on our radar and I will thus create a dev ticket for it immediately. We can then get a developer to take a closer look at all this and, if there’s indeed a code-side limitation like there appears to be, then we can proceed to releasing a fix for it.

I don’t have an ETA when such a fix would be made available, but I will create the ticket for this bug and speak up about the importance of this feature.

Let me know what you think about all of this, and thank YOU for hanging on so patiently (especially here over the weekend, for example) and for putting this bug on our radar.

Sincerely,
George

[Mad Dog]

Thanks for trying. Sounds like the change to Multiple Organizers should could have something to do with this. Oddly, I just noticed another similar support post that looks like it might have a solution…..is that possible?

Make organizer email required

[George]

Thanks for sharing that link @Mad Dog! I think this is just a case of Brian being smarter than me 🙂 Sorry about that – definitely give his snippet a try and let me know if it helps!

— George

[Mad Dog]

Yeah, right…

Anyway, looking at it closer I’m not sure that it will help. It’s identical to what I’m using except he broke out the Venue required function from the main one. Maybe that makes a difference but I also wonder if he’s tested it with a Saved Venue. The ticker is closed so I can’t jump in and ask. And to be honest, at this point I’m going to let it go with Organizer Name and Venue Name being required. The other two fields….well, I’m cheating and it says they’re required even though they’re not being validated. (:}) I’ll see if I get away with that!

Thanks for sticking with me on this.

MD

[George]

Hey @Mad Dog,

Do you mean that you haven’t yet tried his recommended code? If not, I’d recommend trying it – it is different than your code, and while I agree not in a major way, still in a substantive way. His code addresses the new Array structure for organizers that is the key to getting this to work, since our organizer system now enables multiple organizers instead of just one.

If you haven’t tried it, I’d recommend you do – let us know if it’s the “nail in the coffin” and finally does the trick! If it still fails, then, well, first of all: sorry to get your hopes up! 🙂 But if it fails or if you’d rather just genuinely close up this thread for a later day, let me know and we can do that too.

Cheers!
George

[Mad Dog]

Venue is the more important one to me and his code looks identical to what I had unless I’m overlooking something. It’s the one that’s been triggering the validation error all along. Can you see something different in his Venue function code than what I had?

Thanks

[Mad Dog]

Okay, I tried adding his Venue validation function even though I swear it’s identical. And yes, I removed Venue from the existing validation. No joy. If I use a Saved Venue I still get the validation codes saying Venue Name and Venue City are required. So you know, this is what I added per the other post:

add_filter( 'tribe_events_community_required_fields', 'tribe_ommunity_required_fields_venue_city', 10, 1 ); 
  
function tribe_ommunity_required_fields_venue_city( $fields ) {
       
    if ( empty( $_POST['venue']['Venue'] ) )
        $fields[] = 'Venue Name is Required';
          
    if ( empty( $_POST['venue']['City'] ) )
        $fields[] = 'Venue City is Required';
     
    return $fields;
}

I’m curious if it works for him using a Saved Venue but as I said, that thread is closed so I can’t ask.

I have more important Events fish to fry….so onward! Thanks for sticking with me this far.

MD

[George]

Thanks for clarifying about how Venue-related checks were more important for your site – sorry about my misunderstanding there, I had it the other way around in my head and thought the Organizer email was of most importance.

With all this in mind, then, you are right that the Venue-specific code is not much different. And unfortunately, there is not a solution at this time 🙁

Thank you for your continued patience and persistence with this thread. Best of luck with the other Events fish you have to fry, and stay tuned to plugin updates as we’re always improving things and our conversation here has revealed an area of improvement for the Community Events plugin that we can hopefully – and promptly – fix.

Cheers!
George

[Mad Dog]

Oh well….validating the venue info is more important and it’s puzzling why in that other thread he said that required venue information snippet works. Oh well…..not the biggest thing. And I’ve done so much other nice TEC customization for the client all is good. Thanks again for following up with this and sorry it took so much back and forth at times to be clear about the problem.

MD

[George]

Thank you for your patience, too, @Mad Dog – I’ll close up this thread but please keep an eye on plugin updates as we are now aware of some bugs here and will try to get fixes for them into the next few public releases.

Cheers!
George

[Author]

Posts