[Stephen]

Hi Casey,
We built custom meta boxes into our theme, and the issue affected them as well. Our solution worked to fix that. You can close the thread, but I wouldn’t say it is resolved.
Thanks

[Stephen]

Hi Casey,
We deactivated WordPress SEO, and the issue still remained with all the other custom post meta on an event.

[Stephen]

Hi Casey,
We found that it wasn’t an issue with Yoast, it just made the problem worst. We have found an issue in the function publishAssociatedTypes which is on line 2836 of the-events-calendar.class.php

The issue is that the wp_update_post( $venue_post ); and wp_update_post( $org_post ); functions, in addition to updating the Venue and Organizer post status, will also copy all metadata from the Event into the Venue / Organizer.

There is info detailing this behaviour on http://codex.wordpress.org/Function_Reference/wp_update_post

Our solution would be to replace:

wp_update_post( $venue_post );

with:

global $wpdb;
$wpdb->update(
$wpdb->posts,
array(
‘post_status’ => ‘publish’
),
array( ‘ID’ => $venue_post->ID ),
array(
‘%s’,
),
array(
‘%d’
)
);

and

wp_update_post( $org_post );

with:

global $wpdb;
$wpdb->update(
$wpdb->posts,
array(
‘post_status’ => ‘publish’
),
array( ‘ID’ => $org_post->ID ),
array(
‘%s’,
),
array(
‘%d’
)
);

Is this something your team is aware of?

Thanks

[Stephen]

Hey Casey,
No, I still haven’t figured it out, perhaps your development team can reach out to the Yoast SEO plugin developer to figure out the issue. I’m surprised you haven’t heard for Yoast SEO it has almost 10 million downloads: https://wordpress.org/plugins/wordpress-seo/

I would imagine that someone else has used this combinations of plugins.
Thanks!

[Stephen]

Hi Casey,
I believe I have the issue resolved now. What was causing the issue was that the function that generates the dropdown list of venues, on the form, was failing because it ran out of memory. I have over 440 Venues, so when the function would load the venues it would fail. W3 Total Cache must use more memory when the user is not logged it, which pushed it over the edge. It would have likely happened even without W3 Total Cache eventually as my list of vendors grew. I increased the PHP memory_limit and that resolved the issue.
Hopefully this will help if someone has a similar issue.

[Stephen]

Getting closer to a solution, my theme has the template files for the community plugin and it looks like this function tribe_community_events_venue_select_menu( $event ); in venue.php in the modules folder is breaking the page.

[Stephen]

Hi Casey,
I switched to the 2013 theme and the page appears.

[Stephen]

This reply is private.

[Stephen]

So I was able to de-register the problematic function with the following code (hopefully it will show):
add_action(‘init’, ‘custom_unregister_functions’);
function custom_unregister_functions() {
$pro_instance = TribeEventsPro::instance();
//unregister
remove_action( ‘wp_loaded’, array( $pro_instance, ‘allow_cpt_search’ ) );
}

Then I just set the register post type variable to ‘exclude_from_search’ when I was using the now-working tribe_events_register_venue_type_arg filter. I considered this to be a preferable solution to registering the post type all over again (in what would have been it’s third registration). Hopefully that chain of events will be restructured to play more nicely, as you said, in future versions of the Events Calendar Pro add-on.

[Stephen]

So I suppose now I am looking for a way to either:

1) Fix the allow_cta_search() function to use the arguments supplied to the tribe_events_register_venue_type_args filter

or

2) prevent the allow_cta_search() function from running without having to hack the Events Calendar Pro plugin

Any help you could provide would be much appreciated. Thanks again.

[Stephen]

Hey again Barry,
Update, I think that the allow_cta_search() function is the culprit. If I prevent that function from running, the tribe_events_register_venue_type_args filter seems to work fine.

[Stephen]

sorry, the Events Calendar Pro function I’m referring to is allow_cpt_search()

[Stephen]

Hello Barry.
Thanks for the reply. I’ve continued digging into this and my best guess at this point involves the function on line 1446 events-calendar-pro.php
It looks like this function re-registers the “Venues” custom post type to change the argument for “exclude_from_search”, but I am guessing that it uses the pre-filtered venue arguments and, as such, does not include any changes made by the tribe_events_register_venue_type_args filter.

[Stephen]

Actually, what appears to be happening is that the Events Calendar Pro plugin, when activated, is preventing the overwrites added with the tribe_events_register_venue_type_args filter from taking effect. Perhaps the Pro add-on is overwriting the post type arguments with it’s own defaults later in the initialization. I’m not sure, either way it doesn’t look like the tribe_events_register_venue_type_args filter functions as intended with the Pro add-on. Would that fall more under the support / bugfixes scope?

[Stephen]

Thanks Barry,

Could you possibly provide a basic example of changing one post type variable using the tribe_events_register_venue_type_args filter? I am familiar with using WordPress’ filters and actions however, in this case, the registered “Venue” post type does not appear to be using my modified variables.

[Author]

Posts