| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
l7-protocols
|
|\ \ \ |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
etc/inc/easyrule.inc
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Allows to use different block lists by using symlinks to the
easyrule CLI script
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Block rules added with easyrule block.... can now be listed and removed using
the easyrule tool. This is handy to be used with external IDS like tools, e.g
fail2ban.
|
|\ \ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \ |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
while making a fix today I noticed that I had done these early-on and
had not tabbed out the HTML nicely...
|
| | | | | | |
| | | | | | |
| | | | | | | |
Bug #4730 - the code was not there yet.
|
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | | |
redirect user to services_captiveportal_zones.php when an invalid zone is passed
|
|\ \ \ \ \ \ |
|
| | | | | | | |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
from services_dhcp.
This looks like it is wanting curlies to put all clear_subsytem_dirty inside the "if".
|
|\ \ \ \ \ \ \ |
|
| |/ / / / / / |
|
|/ / / / / / |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
There are many more possible flags, documented on the wiki: https://doc.pfsense.org/index.php/Wireless_Status
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
a) When we are doing combined fields and usecolspan2 is in effect, then usecolspan2 is also a signal that we want to spread the combined fields horizontally in a single row. In that case we want the combined fields to all be in a single "tr" tag enclosing them all. That was already working in that way.
b) But if usecolspan2 is NOT in effect, then we want the combined fields to still run "together" but vertically under each other. In this case we want each field to be in its own "tr" tag.
This change makes (b) happen.
If combinedfields is not set, then each of the "if" tests here still follows the same path it did previously, so there should be no effect on the HTML output for any ordinary package fields.
These are changes for master that correspond to https://github.com/pfsense/pfsense/pull/1672 on RELENG_2_2.
|
|/ / / / / / |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Actually the "tr" tag needs to be a single tag-pair that encloses all of the set of fields with combinedfields specified - combinedfields=begin is where the "tr" tag starts and combinedfields=end is where the "tr" tag ends, enclosing a whole set of combined fields.
That allows usecolspan2 to work.
In the previous change I had made it enclose every field in its own "tr" tag-pair That caused usecolspan2 to be ineffective at spreading the combined fields across the display.
Also colspan needs to be initialised each time around the loop - it was getting applied to all fields further down the page after the first one it was used in.
This is the version for master.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When specifying combinedfields begin and end in a package XML file, IE reports some unexpected start tag messages. This is because some "td" tags are not enclosed in "tr" tags in these cases, both at the begin and end of the combinedfields table that is generated. Firefox seems to be forgiving of this.
This has been investigated because BBscan177 who is developing pfBlockerNG is trying to use the combinedfields feature and it was not working so well. I will ask him to try these changes for RELENG_2_2 and confirm that they work.
When combinedfields is not set, then the code path with this change results in the same HTML being output as previously, so it should not change the HTML generated for packages that do not use combinedfields - i.e. I claim not to have broken anything else :)
|
| | | | | |
| | | | | |
| | | | | | |
I broke the syntax!
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The syntax of these all seems good. Because the 2.3-DEVELOPMENT master
does not currently have get_pkg_info implemented, the available packages
tab always says "Unable to retrieve package info...".
But I don't think I broke any code.
This is integrated with the little changes for startdisplayingat var in
pkg.php
|
|\ \ \ \ \ \ \ |
|