Ok, after a little more digging, it seems like the problem is that the main query for returning posts is never fired.
I used define( 'SAVEQUERIES', true );
to show all of the queries there were executed for each page. On a regular archive page that is working correctly, I see a query that looks like this:
SELECT SQL_CALC_FOUND_ROWS wp_posts.*
FROM wp_posts
WHERE 1=1
AND wp_posts.post_type = 'post'
AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'private')
ORDER BY wp_posts.post_date DESC LIMIT 0, 10
Followed by SELECT FOUND_ROWS()
. However, on my taxonomy page (the one that comes up blank), there is no query that is selecting from wp_posts
. I still see the SELECT FOUND_ROWS()
query, but the query immediately preceding isn’t getting any posts. It looks like this:
SELECT wp_term_taxonomy.term_taxonomy_id
FROM wp_term_taxonomy
INNER JOIN wp_terms USING (term_id)
WHERE taxonomy = 'my-custom-taxonomy'
AND wp_terms.slug IN ('taxonomy-term')
This is really baffling to me, and if anybody has any idea what could be the cause of this, I would really appreciate it. Thanks.
I just updated to Beta 3 and this is still broken. I feel like I must be doing something wrong, but the fact that I works perfectly in 3.2.1 makes me think this is a WordPress bug.
Is anybody else experiencing issues with custom taxonomies?
Ok, I feel like an idiot. I just deactivated one of my plugins, and now the taxonomy pages are working perfectly again. Must be a bug with that plugin then. Sorry for taking anyone’s time.
Dominic, what was the plugin causing the issue? That is if you can still remember after 8 months.
@atreidex, I’m pretty sure it was Shopp. It was around then that I switched from Shopp to WooCommerce (which I love).
3.3 is well out of beta now.