Single ticket view template

Hi,

I know the document is lacking (nonexistent actually) and we will work on it very soon. Sorry about that.

If you want to customize the details template, what you have to do is to create one that’s called single-ticket.php. I can see you tried that already but that’s the way it is supposed to work. I’ll run some tests later today to see if I can find a bug.

Anyways, once this new template is created, instead of using the_content(); like in a normal template you have to use wpas_get_template( 'details' );

Thank you for the reply. Yes having a single-ticket.php doesn’t work.

Then i checked the function-templating.php and found this code.

/* Get template name */
	$template_path = get_page_template();
	$template      = explode( '/', $template_path );
	$count         = count( $template );
	$template      = $template[$count-1];
	/* Don't apply the modifications on a custom template */
	if ( "single-$slug.php" === $template ) {
		return $content;
	}

If I am not wrong, It seems, it will only return the page template. Now sure how it will check for single-ticket.php. (isn’t the $template parameter going to be page.php all the time?)

Thank you for your reply and for this awesome plugin.

One of the things this function does is check if the current template for the loaded page is single-$slug.php where $slug is the post type ticket (this is actually a useless thing to use the $slug var, will change that).

So if the current template is single-ticket.php the function doesn’t do anything at all as everything is supposed to be done in the custom template (single-ticket.php) directly.

Thank you for your reply.

Strange I am not able to make it work. Have you had some time to do any tests on this please?

Thanks,
Bage.

Heh. I got it. Stupid mistake.

What happens is that there is a previous filter that switches from single.php to page.php (if available) to get rid of the comment form, categories, tags, etc. However, this filter didn’t check if the current template was already a custom one.

I have pushed the fix to the development branch but I won’t be able to push an update to WP.org now. I suggest you apply the fix manually for now and it will be fixed in 3.1.2. See commit 3a592bc4dd for details.

Thank you.

Thank you very much for your valuable time and for this awesome plugin.

Don’t forget to leave us a 5 stars then ??