Use original element (<div>/<small>) with "data-for" attribute.
The old jquery "for" attribute selectors can be removed once conversion to "data-for" attribute is complete (including plugins).
The old jquery selectors to remove once conversion is complete.
opnsense_ui.js & head.inc
$("*[for='" + $(this).attr('id') + "']")....
$('[for*="help_for"]')....
With this, there is consistency in setting the default route
and associated marker file. Nothing is done before the decision
is final, so we may not end up with a missing route after an
attempt to reconfigure for something that doesn't work anyway.
DHCPv4 and PPP still do this manually, but we will have to route
them through the same logic instead of them manually handling their
routes. 6rd and 6to4 may have a similar issue as well.
While here, swap the system_routing_configure() arguments to
align with the way other configure functions present their
arguments (verbose print flag first).
Gateway monitoring and default switching improvement since 2016.
Push $keep into default handling, it may be useful in general to
avoid spurious switches. It could also be a default probably.
ended up realising the function is totally whacky from top to
bottom. Writing default file hints before doing lookups for
said IPs, writing empty fallbacks, missing logging info.
To be continued.
Introduced in 2005 to separate good VLAN-capable driver from
the bad ones. We wonder how relevant this is nowadays.
Breaks at least Xen where the driver fails to pass the host's
VLAN capabilities.
Discussed with: @adschellevis
This change consists of two components:
1) enforcing the user to change his or her password every x days, when pwd_changed_at is not set or longer ago then specified only access to the password page is prohibited
2) enforce minimal length or complexity settings depending on selected choices
* Allow clearing configd log in clear all
* Neither configd nor lighttpd remote exists
These things will have to wait till syslog-ng is properly integrated.
