Thank you Ismael, I ended up creating a shortcode for it instead which allowed me to position the tags anywhere in the content instead which is a bit more flexible.

I am sharing my code bellow in case someone wants to do the same:

function psc_pagetags( ){
	$t = wp_get_post_tags(get_the_ID());
	
	foreach ($t as $e) {
		$psc_tags .= '<a href="' . get_tag_link($e->term_id) . '">' . $e->name . '</a>';
		if($e != end($t)) {
			$psc_tags .= ', ';
		}
	}
	
	return $psc_tags;
}
add_shortcode( 'psc_page_tags', 'psc_pagetags' );

By using the shortcode [psc_page_tags] you will get a comma delimited list of linked tags for the current post.

Cheers,

I can understand your logic and agree. It may be an issue to work around but it is still an issue.

I do not agree that the page should be a 404 if you understand what a 404 actually implies technically so your assessment is wrong.

I’m happy to work around this by not providing a list view which will make it less likely for users to come up with the issues but that doesn’t remove the issue. There is a bug somewhere as the wrong template is being interpreted and looking the other way or working around it, while it may provide a quick way to not worry about it much will not make the issue go away.

I would appreciate a little more professionalism in dealing with the matter at hand and if it is in fact outside of the scope of what you are able to help with yourself, please escalate to someone able to make a better informed resolution of the matter.

Respectfully yours,

Thank you, that does work.

Perfect.

Thank you!

Perfect, exactly what I wanted.

Thanks!

I have now enabled file editor.

Cheers,

4454 is the post ID. I am using this permalink format:

/%post_id%/%postname%

Ok I was able to figure this out. My problem was that I was using the slug for the custom post type and NOT the slug for the custom taxonomy.

Thanks.

None of the above plugins is a fit solution.

Both cause some serious load issues and the first one even breaks a lot of my urls (they end up in endless loops).

Thank you. That did the trick.

Nevermind, I was able to figure it out by the help of another post. Here is the correct code in case someone is trying to do the same thing:

// Add Avia Layout support for custom post type Comercios
add_filter('avf_builder_boxes','custom_post_types_options');

function custom_post_types_options($boxes)
{

	$boxes = array(
		array( 'title' =>__('Avia Layout Builder','avia_framework' ), 'id'=>'avia_builder', 'page'=>array('portfolio','page','post','comercio'), 'context'=>'normal', 'priority'=>'high', 'expandable'=>true ),
		array( 'title' =>__('Layout','avia_framework' ), 'id'=>'layout', 'page'=>array('portfolio', 'page' , 'post','comercio'), 'context'=>'side', 'priority'=>'low'),
		array( 'title' =>__('Additional Portfolio Settings','avia_framework' ), 'id'=>'preview', 'page'=>array('portfolio'), 'context'=>'normal', 'priority'=>'high' ),
		array( 'title' =>__('Breadcrumb Hierarchy','avia_framework' ), 'id'=>'hierarchy', 'page'=>array('portfolio'), 'context'=>'side', 'priority'=>'low'),
	);

	return $boxes;
}

Ok, that’s great. I will do that. Hopefully this can be included in a future update so that I don’t lose my modification.

Thanks again for all your help!