[Josh]

Hey John,

No problem! Happy to help.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Annarosa,

No problem. Happy to help.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Joseph,

Definitely understandable about the second option.

For the meta value, there isn’t a field on the admin side of things where this would be displayed however you could try Advanced Custom Fields and create a new field group to display only on the single organizer view that has a field with the name of “_OrganizerFacebookID”  (not field label).

Alternatively, if you have access to phpMyAdmin or similar solution for your site, you could update the postmeta table to include that value for the associated organizer WordPress IDs.

Let me know if this helps.

Thanks!

[Josh]

Hey Nicole,

No problem, definitely understandable!

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Tac,

No problem, let me know how it goes.

Thanks!

[Josh]

Hey Brian,

Unfortunately we have a strict policy against accepting or using login credentials for customer sites.

But, to help get to the source and ensure we’re looking at the right thing here, can you verify whether or not the additional fields for the tickets work if we have Checkout Fields Manager plugin disabled?

Thanks!

[Josh]

Hey Kelly,

Thanks for reaching out to us!

Take a look at the Pro > src > views > pro > single-organizer.php file. You can take advantage of one of the “do_action” hooks and hook a function which includes your shortcode to that chosen action. You could also follow our Themer’s Guide and copy that file into your theme and place the shortcode output where you would like directly to the template.

Let me know if this helps.

Thanks!

[Josh]

Hey John,

Thanks for reaching out to us!

Try changing:

$Woo__Tickets = Tribe__Events__Tickets__Woo__Main::get_instance();

to:

$Woo__Tickets = Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance();

and see if that works for you now.

Let me know if this helps.

Thanks!

[Josh]

Hey Thierry,

I’m glad you were able to find a solution that worked for you here!

The subscription covers access to the Pro version of the plugin which includes the features described here as well as access to updates to the plugin that help to ensure compatibility with WordPress as well as the core Events Calendar plugin.

Let me know if this helps.

Thanks!

[Josh]

Hey Tac,

It looks like the issue here is that the payments are trying to be split between the same account ([email protected]). When setting up the merchant account, ensure that the email address is different than the Community organizer that is trying to have the payment split for.

Let me know if this helps.

Thanks!

[Josh]

Hey Annarosa,

Thanks for reaching out to us!

It sounds like loop that is getting added to the home page is a custom loop and isn’t the default WordPress loop like you would find if your home settings under Settings > Reading tab within the WordPress settings were set to the latest posts.

When you select the category for the settings you describe, is there a way to choose post types within those settings as well?

Thanks!

[Josh]

Hey John,

Thanks for reaching out to us!

For this, you can try taking advantage of the built-in  “remove_meta_box” function from WordPress and conditionally only run it if the logged-in user is not an administrator.

Let me know if this helps.

Thanks!

[Josh]

Hey Phillip,

Thanks for reaching out to us!

Try adding the following snippet to your theme’s functions.php file to see if it helps with some of these permission type of issues:

function ce_capabilities_resolution() {
$anon_users = Tribe__Events__Community__Main::instance()->anonymous_users;
add_action( 'tribe_events_community_form', array( $anon_users, 'add_venue_org_caps' ) );
add_action( 'tribe_ce_before_event_submission_page', array( $anon_users, 'add_venue_org_caps' ) );
add_filter( 'user_has_cap', array( $anon_users, 'filter_venue_org_caps' ), 10, 3 );
}

add_action( 'init', 'ce_capabilities_resolution' );

Let me know if this helps.

Thanks!

[Josh]

Hey Greg,

As a quick check here, could you try setting an end date for the recurrence (within a 2 year range maybe ) rather than the “Never” option there to see if that changes anything for the exclusion in this case?

Thanks!

[Josh]

Hey,

No problem. I’ll leave this thread open for now. If you see the issue creep back up over the next week or so you can update the info here.

Thanks!

[Author]

Posts