From fd41f7e4bc61e08b654dec67eda53ab52cbb257b Mon Sep 17 00:00:00 2001 From: Nathan Gray Date: Mon, 8 Apr 2013 13:18:27 +0000 Subject: [PATCH] In the rare case where the app specifies both select options in both the sel_options and the nextmatch options-name, try to avoid overwriting --- etemplate/inc/class.etemplate_widget_nextmatch.inc.php | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/etemplate/inc/class.etemplate_widget_nextmatch.inc.php b/etemplate/inc/class.etemplate_widget_nextmatch.inc.php index f04fed1c30..4f517c4233 100644 --- a/etemplate/inc/class.etemplate_widget_nextmatch.inc.php +++ b/etemplate/inc/class.etemplate_widget_nextmatch.inc.php @@ -192,7 +192,11 @@ class etemplate_widget_nextmatch extends etemplate_widget if(strpos($name, 'options-') !== false) { $select = substr($name, 8); - self::$request->sel_options[$select] = $_value; + if(!self::$request->sel_options[$select]) + { + self::$request->sel_options[$select] = array(); + } + self::$request->sel_options[$select] += $_value; // The client doesn't need them in content, but we can't unset them because // some apps don't send them on re-load, pulling them from the session //unset($value[$name]);