new port-search wildcarding - bad idea?
* for an exact match use "quoting", a bit like what Google does to enforce a search term * otherwise terms are assumed to be wildcard bounded and case insensitive * without quotes, * and ? characters are supported for multi and single character wildcards. we could revert this commit if we don't like it.
This commit is contained in:
		| @@ -14,7 +14,7 @@ | ||||
|       <td>[% row.alias | html_entity %]</a> | ||||
|       <td>[% row.dns | html_entity %]</a> | ||||
|       <td class="nd_center-cell"><a class="nd_linkcell" | ||||
|         href="[% device_ports %]&q=[% params.q | uri %]&f=[% row.port | uri %]">[% row.port | html_entity %]</a></td> | ||||
|         href="[% device_ports %]&q=[% params.q | uri %]&f=%22[% row.port | uri %]%22">[% row.port | html_entity %]</a></td> | ||||
|       <td>[% row.device_port.name | html_entity %]</td> | ||||
|       <td><a class="nd_linkcell" | ||||
|         href="[% search_device %]&ip=[% row.subnet | uri %]">[% row.subnet | html_entity %]</a></td> | ||||
|   | ||||
		Reference in New Issue
	
	Block a user