Brook

Howdy Ann4,

It sounds like you are trying to do something like this snippet does: https://gist.github.com/elimn/c47fb3e65d437c2479bd

Is that so? Or are you trying to prevent the creation of event categories for specific roles?

Cheers!
– Brook

Howdy laetitia Godet,

I am sorry to hear that error is popping up. We have seen one other person with a similar issue, but in spite of our best efforts were unable to replicate or find the cause. The tricky thing was the person was entirely unwilling to do a conflict test, which is one of the primary diagnostic tools needed to fix this.

Would you be able to do a conflict test? This guide walks you through how to test for a conflict, and then identify what is conflicting.

Cheers!
– Brook

Howdy jjbte,

There might be an glitch with tribe_settings_sent_data. That new option does override the other options, it is intended to preserve settings when you submit multiple ones but one of them had an error. It remembers the other settings you had changed. However, one of our team members saw something similar to you, that it was remembering things it should not have and silently using those settings instead. We all tried very hard to reproduce and isolate this but have not been able to yet. We will keep at it of course until we can find the problem and fix it.

Since you are clearly skilled with databases my advice would be to delete tribe_settings_sent_data. You might make a backup first just to be safe, I always do with live data.

Thanks for opening your own topic by the way. I saw your other one where a moderator requested you split, no worries about posting there! But we really appreciate you splitting it up.

In that other topic I mentioned doing a conflict test. Timezone issues like this are frequently caused by plugin conflicts. Suffice to say it is very easy for one plugin to accidentally ruin all plugins Timezone calculations and it happens rather often. WordPress has guidelines for how to avoid this, but not all plugin devs are familiar with them. In order to proceed you might test if a “conflict” is happening, and if so narrow it down so a fix can be found for it. This guide walks you through how to test for a conflict, and then identify what is conflicting.

Cheers!
– Brook

Thanks for the feedback laudio. We really appreciate folks reaching out when a tutorial needs updating. 🙂 Cheers!
– Brook

Howdy again,

It’s my pleasure! Performance is definitely on our radar. It’s more always on our radar. Like most software companies we build new features, then cycle back to optimizing them and everything they affect for speed. We have just started a performance cycle and have so far found a couple improvements that are tentatively scheduled to be ready in the 4.2 and 4.3 versions. The 4.2 one primarily affects people with tens of thousands of posts in wp_posts, and can shave a little bit off each events page load. The 4.3 one only affects Pro users.

We’ve also looked at raw query log for one ‘troublesome day.’ It’s a ton of queries to go through. We didn’t find any particular query type which was problematic. Rather, it was a gradual progression from normal query times, to all being very, very slow, over the span of about 20 minutes. This was for all queries. It was basically a ramp-up curve.
These site issues occurred 4 times this month, and there is no apparent correlation to admin activity, or traffic spike. After restarting the server, things appeared to go back to normal, until the next spike.

It sounds like your server might have a runaway process. Perhaps something that slowly consumes more and more of the CPU over time, or more memory? If you have as much control over the server as it sounds like you do I would first try to isolate what resource is bottlenecking during those spikes. If your CPU or RAM is showing extremely high usage, see if you can examine the processes to find one or more that are consuming inordinate amounts.

As far as performance tuning goes you might double check that all of your WP tables are using the InnoDB engine storage engine and that you have tuned InnoDB for your server. In particular setting innodb_buffer_pool_size to something balanced for your needs. A lot of servers set it to a number insanely low like 8M. If your server has the RAM to spare you might as well fill it up with more than 8 megabytes of your database.

Quick note about 3 out of 400K = it is possible that people aren’t really concerned if the site slows down a bit, and only notice when something fails and extensive digging for root cause has to take place.

Absolutely. We definitely do not use reports as absolute indicators of how widespread an issue is. But still 3 is a very low number of reports compared to typical issues, and that is something we have to factor in when prioritizing fixes. We do want to fix the month view cache issue, but it is not our highest priority bug at the moment.

Cheers!
– Brook

Howdy Richard,

Thanks for sharing the code. I appreciate you’re trying to narrow it down to one line.

I tried your code on my own custom post type and I am not seeing any issues. :-/ In an effort to make things as simple as possible I just copied the example Custom Post Type from the Codex. Here’s my full code:

add_action( 'init', 'create_post_type' );
function create_post_type() {
	register_post_type( 'acme_product',
		array(
			'labels' => array(
				'name' => __( 'Products' ),
				'singular_name' => __( 'Product' )
			),
			'public' => true,
			'has_archive' => true,
		)
	);
}

add_action('init', 'setup_cpt_filters');
function setup_cpt_filters() {
	// globalize it so that we can call methods on the returned object
	global $my_cpt_filters;
	// We'll show you what goes in this later
	$filter_array = array(
		'esc_featured_on_homepage' => array(
			'name' => 'Featured on Homepage',
			'meta' => 'wpcf-feature-on-homepage'
		)
	);

	$my_cpt_filters = tribe_setup_apm('acme_product', $filter_array );
}

When I update or post something to my Custom Post Type there are no errors shown, the nonce appears to work as expected.

This might be a conflict with the toolset plugin. Perhaps it has its own actions or hooks that are not playing well with APM ? I don’t have a license to that plugin so I can’t test it.

To narrow it down a bit have you tried doing a conflict test? Obviously you can’t disable WP Toolset or APM just yet, but have you tried disabling everything else and switching to a default theme? Does the issue persist? If so, what happens if you disable WP Toolset and try the above code?

Thanks again Richard for your thoroughness in providing info. Cheers!
– Brook

I appreciate the feedback. Thanks for getting in touch about this.

– Brook

Howdy Csem,

Our plugin just uses the WP Standard CPT Archive page. There is no shortcode to embed this content elsewhere, rather it just resides where WordPress puts it. It’s much like any other Archive page WordPress creates, such as the category pages or a page to view all tags with a given post. WordPress does not allow you to embed these via shortcode either.

But you can change the slug of the page in WP-Admin > Events > Settings. And of course you can customize the page to your hearts content, adding content and such, via a theme override. Have a look at the Themer’s Guide. It walks you through modifying the PHP templates so you change the look of things.

I hope that info helps. Cheers!
– Brook