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:
@@ -40,7 +40,7 @@
|
||||
[% END %]
|
||||
<td>Switch Port</td>
|
||||
<td><a class="nd_linkcell"
|
||||
href="[% device_ports %]&q=[% node.device.dns || node.switch | uri %]&f=[% node.port | uri %]&c_nodes=on&c_neighbors=on">
|
||||
href="[% device_ports %]&q=[% node.device.dns || node.switch | uri %]&f=%22[% node.port | uri %]%22&c_nodes=on&c_neighbors=on">
|
||||
[% node.switch | html_entity %] - [% node.port | html_entity %]</a>
|
||||
[% ' <i class="icon-book text-warning"></i> ' IF NOT node.active %]
|
||||
[% IF node.device.dns AND node.device_port AND node.device_port.name %]
|
||||
|
||||
Reference in New Issue
Block a user