Connect Template to Archive with Extending Post Type

Bill-

You found an interesting issue. That check is based on how Pods registers the custom post type, but since it didn’t with an extended post type, it will always throw a warning with extended post types. I need to fix that in the next version.

For now, if portfolio already supports archives, you can just ignore that warning, it will go away in the next revision of this plugin. If it doesn’t support it, you will need to add it with something like this:

add_action('init', 'my_custom_init');
function my_custom_init() {
	add_post_type_support( 'portfolio', 'archive' );
}

The following is an archive page is it not?
https://www.coachestoronto.com/wordpress/blog/portfolio_category/restaurants/

Here I have the custom fields set to appear above the content, but they do not show as they do here on the single post page:
https://www.coachestoronto.com/wordpress/blog/portfolio-items/miller-tavern/

The added fields are the address and website.

The fields also do not appear here in a portfolio grid,
https://www.coachestoronto.com/wordpress/restaurants-test/
but I assumed that meant this page was not archive based.

This is a charity website project — so all for a good cause.

Cheers, Bill.

I don’t know for sure by looking at the URLs, but I would assume that https://www.coachestoronto.com/wordpress/blog/portfolio_category/ is a custom taxonomy archive, not a custom post type archive. I’m not really sure, as I’ve never used this theme.

You could test with something like this:

<?php
add_action( 'wp_head', 'slug_test_archive' );
function slug_test_archive() {
if ( is_tax() ) {
echo 'is taxonomy!';
}
elseif ( is_post_type_archive() ) {
echo 'is post type archive';
}
else {
global $wp_query;
print_r( $wp_query->query_vars );
}

That will tell you if you are on a taxonomy or post type archive or if not it will print the current query vars and from there you should be able to figure out what is going on.