[Nico]

Thanks for following up Brendan!

I just searched our backlog and couldn’t find any bugs related to json+ld data being incorrect.

Can you please share your system information with me so I can check this?

Please do send system information in a private reply (this doesn’t mean admin user / pass, if you are not sure about it follow this link), I would like to inspect it before trying to reproduce this in my end.

Best,
Nico

[Nico]

Thanks for following Tac! Hopefully we are almost there 🙂

I just confirmed with a team mate that the code is working for both of us. So can you please test this with Tweenty Sixteeen theme and no other plugins active but ours?

Thanks,
Nico

[Nico]

Thanks for following up!

I crafted a sample custom filter for this (not heavily tested). You might need to tweak it a bit to fit your needs, but I guess it’s a good starting point 🙂


/* Tribe, add custom filter to show/hide instances of recurring events */
if ( class_exists('Tribe__Events__Filterbar__Filter') ) {

class Tribe__Events__Filterbar__Filters__Recurring extends Tribe__Events__Filterbar__Filter {

public $type = 'radio';

public function get_admin_form() {
return $this->get_title_field();
}

protected function get_values() {

return array( array( 'name' => 'Show', 'value' => 'show'), array( 'name' => 'Hide', 'value' => 'hide'));
}

protected function pre_get_posts( WP_Query $query ) {

$values = (array) $this->currentValue;

if ( $values[0] == 'hide' ) {
$query->set( 'post_parent', 0 );
}

}
}

new Tribe__Events__Filterbar__Filters__Recurring( 'Recurring Events', 'recurring' );
}


Just paste the code above in your theme’s (or child theme’s) functions.php file, activate the new filter in the admin (Events > Settings > Filters) and let me know if this is what you were looking for,
Best,
Nico

[Nico]

This reply is private.

[Nico]

Thanks for confirming Brad 🙂

To safely store customizations (template override, coded added to the functions.php file, etc) you’ll need to create a Child Theme. It’s super simple → WordPress Codex – Child Themes.

Another way around this is to use a plugin to store code tweaks, for example → Code Snippets plugin. Or you can also develop a custom plugin to store these → WordPress Codex – Writing a Plugin.

Cheers,
Nico

[Nico]

This reply is private.

[Nico]

This reply is private.

[Nico]

This reply is private.

[Nico]

Thanks for the follow-up Vincent! Glad to hear you are comfortable working with code 🙂

Now I see two possibilities:

• Craft unique name for events and venues: as you mentioned, concatenate information to create unique names. Event title would be: ‘Event name + event date’, and venues titles: ‘Event name + event location’. This way you’ll have all unique entries.
• Override core files: this is generally not suggested but as this would be a temporary patch to batch import the initial data of the site I see no problem in doing this. The files controlling the imports are ‘wp-content/plugins/the-events-calendar/src/Tribe/Importer/File_Importer_Events.php’, and in the same path ‘File_Importer_Venues.php’. The method match_existing_post of each Class (file) is the check for duplicates, you can modify the code (in both files) to:
  
protected function match_existing_post( array $record ) {
return 0;
}

  and try to import the data again, hopefully it will crate the exact amount of events and venues you have.

You can also combine both options if you need to! Also, I think it’s a great idea to tag or categorize all imported events just in case you’ll need to do some fixes on the front-end later!

Please let me know if this works for you,
Best,
Nico

[Nico]

This reply is private.

[Nico]

This reply is private.

[Nico]

You are right, sorry I missed it!

Just remove the first part of the selector and also target the link directly:

.tribe-this-week-widget-day .tribe-venue a {
font-size: 13px;
line-height: 1.5 !important;
text-decoration: none !important;
font-weight: normal !important;
}


Please let me know if that works as expected,
Best,
Nico

[Nico]

Hi Barback,

Glad to help you out once again 🙂

I’ve been playing around with this and I was able to find a working solution:

/* Tribe, temporarily override checkout uri to avoid ending in the checkout page */
function tribe_temp_override_checkout_uri ( $uri ) {

/* only change the uri for form process */
if ( ! isset( $_GET['eddtickets_process'] ) || empty( $_POST['product_id'] ) ) {
return $uri;
}

/* return custom uri */
return tribe_get_events_link();
}
add_filter ( 'edd_get_checkout_uri', 'tribe_temp_override_checkout_uri' );


Paste the code in your theme’s (or child theme’s) functions.php file and give it a try. I didn’t extensively test the snippet so be sure you do so before using it in the live site.

Please let me know if it works for your site,
Best,
Nico

[Nico]

Hi there Brian,

Thanks for reaching out to us! This is indeed possible with a template override 🙂

First of all take a look at our themer’s guide for complete details on how to do this! Once you are familiarized with the process create a template override for the file: ‘wp-content/plugins/event-tickets/src/views/tickets/rsvp.php’ and once the copy of the file is in the appropriate place in your theme (or child theme) folder just replace the content for this customized version:

https://gist.github.com/niconerd/b31d7d436a35e15a1f0c151f9a0bc7bb

Please give this a try and let me know if it works for you,
Best,
Nico

[Nico]

Hi Joslyn,

Thanks for reaching out to us! Unfortunately we are not able to provide support in the pre-sales forum 🙁

We are happy to assist our premium users with support issues via our premium forums, please log into the account that has been created when the purchase was made. If you have not purchased one of our premium plugins, you can post in our open source forum. We review that forum weekly, mainly for bug reports.

I’ll go ahead and close out this thread, but please do post in the appropriate forum and we will be happy to assist you.

Best,
Nico

[Author]

Posts