From 07fc3e4bbfd9e849545131b80e2a512f3f4857a6 Mon Sep 17 00:00:00 2001
From: Nathan Gray <nathangray.bsc@gmail.com>
Date: Mon, 9 Feb 2015 20:47:18 +0000
Subject: [PATCH] When changing the nextmatch row template, don't query the
 database right away since re-initializing the nextmatch controller forces
 another query.

---
 infolog/inc/class.infolog_ui.inc.php | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/infolog/inc/class.infolog_ui.inc.php b/infolog/inc/class.infolog_ui.inc.php
index 3864e8987b..5af5852ccb 100644
--- a/infolog/inc/class.infolog_ui.inc.php
+++ b/infolog/inc/class.infolog_ui.inc.php
@@ -387,6 +387,7 @@ class infolog_ui
 		}
 
 		// check if we have a custom, type-specific template
+		$old_template = $query['template'];
 		$query['template'] = 'infolog.index.rows';
 		unset($query['custom_fields']);
 		if ($query['col_filter']['info_type'])
@@ -404,6 +405,9 @@ class infolog_ui
 				$query['col_filter']['info_status'] = '';
 			}
 		}
+		// Template change forces the UI to do a full update first, no point in getting rows right now
+		if($old_template != $query['template']) return 0;
+		
 		// do we need to read the custom fields, depends on the column is enabled and customfields exist, prefs are filter specific
 		// so we have to check that as well
 		$details = $query['filter2'] == 'all';