[Mad Dog]

Nice to “see” you too again. Thanks for getting back to me. I’ll post this in Feature Request for sure. I’ll check into Relavanssi if that’s really what the client needs. I’ve tried other plugins that supposedly expand the search for Custom Posts and Fields but they didn’t work like they should have. Maybe this will. In the meantime I’ll add some custom fields to the New Event Notification email so the client can at least get more details that way for now.

THANKS

[Mad Dog]

It works as I have it so I’ll leave it. Let me know if they redo the whole login page error trapping so it works more like we both think it should.

Thanks!

[Mad Dog]

Two questions:

1. Is the only way to add an error message to the login page by using a function?

2. When I do, using login_message doesn’t work.

I can use login_form_bottom to check if the URL parameter login=failed and it works and places a message jusst above the login form, but is there a better way to do this?

// Add LOGIN ERROR  message  to login page
add_action( 'login_form_bottom', 'login_error_message' );
function login_error_message() {
	if (isset($_GET['login']) && $_GET['login'] == 'failed') {
		echo "<div class='login_error'>Login and Password don't match.<br />Please check them and try again.</div><br /><br />";
	}
}

Thanks!

[Mad Dog]

Seems it should be pretty simple to put error checking on the page so it stays there but an error message appears. In fact, I may need to add something to the page to display an error message (by way of the “failed login” URL parameter)so the user knows something happened and doesn’t just wonder what’s going on.

Keep me posted.

THANKS

[Mad Dog]

Excellent idea! Works like a charm. Granted, it’s a bit of a PITA but adding Editor to the user’s capabilities makes their name appear in the user dropdown. An added bonus, you can Bulk Edit Events and since User is part of bulk editing, it’s easy to change a whole batch at once. Then remove Editor from their capabilities. Not something I’d like to do for a lot of users but it worked to do it for a few larger users who have a lot of entries.

THANKS!

[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

[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

[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]

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

[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

[Mad Dog]

Kind of an odd behavior from a user standpoint. If I view a detail page and hit a “Go Back” type link I would expect to return to the page I was just at. Even adding /photo/ isn’t good because it takes you back to the First Photos page, not the one you may have come from.

I changed it to <a href="#" onClick="history.go(-1);return true;"> which I think makes much more sense!

Thanks

[Mad Dog]

Let me pass along a suggestion. On the Theming page, in addition to (or along with) the list of files it would be nice to have the existing directory tree with it. That way it would be easier to know that /the-events-calendar/src/views/single-event.php is the one.

Just a serving suggestion to cut down on support requests!

Thanks

[Mad Dog]

Cancel this request. I found it. There are too many files in too many places in three of your plugins named single-event.php!

• This reply was modified 10 years, 7 months ago by Mad Dog.

[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.

[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!

[Author]

Posts