| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Review alert wording. End sentence with period, remove redundant 'Warning', ↵ | k-paulius | 2016-02-14 | 1 | -1/+1 |
| | | | | | 'Error', etc. prefixes, since alerts are now color coded. Remove <b> tags. | ||||
| * | Synchronize page titles with tab titles. Rename some titles in order to be ↵ | k-paulius | 2016-02-13 | 1 | -2/+2 |
| | | | | | more consistent. Convert page title to title case. | ||||
| * | Status IPsec info box | Phil Davis | 2016-01-27 | 1 | -2/+13 |
| | | | | | | | | | | | | | | | | | | | As well as internationalization of this info box, I have: 1) Made all of them the same text - it seemed odd that there were 2 different versions of text for the same thing. 2) Made it an info-level infoblock. It seemed odd to me that this was showing as a warning - it is really just a helpful info with link. 3) Made it open on page load if IPsec is not enabled, otherwise if IPsec is already enable it loads closed and the user can open and read it if they care. What do you think about this combination of things in the UI? I suspect there are a few other places where there is a convenient link 'You can configure xxx here', but it shows as a warning. If there is agreement about the infoblock approach I have suggested here, then I can do similar in other places. | ||||
| * | Remove all pfSense_MODULE and pfSense_BUILDER_BINARIES definitions, whatever ↵ | Renato Botelho | 2015-12-15 | 1 | -5/+0 |
| | | | | | was the reason they were added, it was never finished and it's not being used | ||||
| * | Code style status* | Phil Davis | 2015-12-15 | 1 | -4/+3 |
| | | |||||
| * | Rename of files to better match their position in the memory structure | Stephen Beaver | 2015-12-11 | 1 | -0/+163 |
 |
index : pfsense | |
| Raptor Engineering's fork of the main repository for pfSense | Raptor Engineering, LLC |
| summaryrefslogtreecommitdiffstats |
|