| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
for isset, the way the values were copied before it would be set to 'false' which was still set, so the code always triggered when it shouldn't. When reading back from XML at boot time it's OK, so only the web interface is affected. Fixes #6010
|
| |\ |
|
| | |
| |
| |
| |
| | |
Seems to be a copy/paste error remain from when i initially created the dhcpd rrd thingy. Just noticed this now ;)
Mar 17 22:33:34 php-cgi rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/opt3-dhcpd.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: /var/db/rrd/opt3-dhcpd.rrd: found extra data on update argument: U:U:U:U:U'
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A place for JavaScript polyfills.
JavaScript string includes method polyfill. A new method that has not yet found it's way into many browser implementations.
Documentation: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/includes
Note: An array & typedarray includes method, that could also be useful, is currently in draft status.
Documentation: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/includes
Documentation: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray/includes
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
This change will allow implementation of workarounds for bugs involving 'An HTTP_REFERER was detected other than what is defined in System' by adding the IP address to the alternate hostnames list, without having to disable protection completely.
This is useful to workaround things like Redmine #5939 and/or enabling access to WebGUI over IPv6 linklocal (fe80::1:1) by adding IPs manually.
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Echoing $pconfig['custom_options'] directly into JavaScript is prone to breaking the script by creating invalid syntax due to characters such as line feeds etc.
Best to transfer a flag from PHP.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Echoing $pconfig['custom_options'] directly into JavaScript is prone to breaking the script by creating invalid syntax due to characters such as line feeds etc.
Best to transfer a flag from PHP.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
pfSense-pkg-Open-VM-Tools on ova
|
| |/ / / |
|
| | | | |
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | |
| | | |
If pppoe_monthly, pppoe_weekly, pppeo_daily or pppoe_hourly was already set, then when editing the PPP interface the advanced fields were not automagically displayed. They should be, because the user needs to see these settings if they are there.
Add these extra checks to the test makes the Advanced fields automagically open correctly in this case.
|
| |\ \ \
| |/ /
|/| | |
|
| |/ /
| |
| | |
Fixes the problem reported by @jimp where the Advanced button for the source port fields would show "Hide Advanced" when creating a new rule from scratch. Now when creating a new rule, it starts off as "Display Advanced" (with the source port fields hidden.
|
| | |
| |
| |
| |
| |
| | |
Corrected showadv logic
Corrected long standing iussue displaying reset times (goes back to 2.0)
Corrected config save by adding hidden ptpid
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Initilize element before refreshing
|
| | | |
|
| |\ \ |
|
| | |/
| |
| |
| | |
Error: The align attribute on the td element is obsolete. Use CSS instead.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
1) Standardize the way the Advanced button works to display and hide the source address/port fields.
2) Remove dstenable boolean - it was always set to 1 (true) and so all the tests that used it were meaningless.
3) Use true and false for portsenabled var rather than 1 and 0 - easier to read/understand.
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
in firewall_rules_edit
1) Put some common code fragments into show_source_port_range() and use code that actually successfully changes the button text Display/Hide. Around line 1808.
2) Make the button itself be hidden when a protocol is selected that does not use source port range (as well as the source port fields being hidden) - line 1908-1909
3) When the user re-selects a protocol that can use source port range, unhide the button and set the button text and hide/unhide of source port fields appropriately depending on the run-time values in the source port fields - line 1900-1905
This standardizes the behavior of the source port Advanced button.
I will do the other general advanced button separately.
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| |/ / /
| | |
| | | |
This is the last piece of code I have for standardizing "advanced" buttons in the UI.
|
| |\ \ \
| |_|/
|/| | |
|
| | | | |
|
| |/ / |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
is unreachable
|
