| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit cb5961d1fa64a45cbec5ef5d677b57f8d62f50b5)
|
|
|
|
|
|
| |
cert or csr is present in the cert
(cherry picked from commit 1048585a08ac824057eea35c57fe359b9e6a48fe)
|
|
|
|
| |
(cherry picked from commit a66177645191359e5ce854d733e9be40ada3535b)
|
| |
|
|
|
|
| |
(cherry picked from commit 821110e8ff76564c23783c554fc89cd9458683ac)
|
|
|
|
| |
(cherry picked from commit 6924a2bf34a70cd33284a28ca3575f33f9834375)
|
|
|
|
| |
provide two examples of server-side code to return the client address. Fixes #6374
|
|
|
|
|
| |
The backslash escaping of the double-quotes here displays the backslashes literal on the GUI. Escaping is not needed in this single-quoted string.
(cherry picked from commit 4ede308c615508a7b70074f56a3ca77cae7b68f1)
|
|
|
|
|
|
|
|
|
| |
If "description_state" is requested here, there are too many "%s" substitutions in the string for sprintf().
Also, to help translators, number all the "%s" substitutions. Then translators can rearrange the text and variable order if they need to.
I removed the commented-out get_service_control_GET_links() while I am here, because it also contained sprintf() strings that had multiple "%s" substitutions. So I had found it when searching for lines containing multiple "%s". Might as well remove it "in the next version" as the comment says.
(cherry picked from commit b3119a61c8f5841f92e2c1fe945f90d9e98a843c)
|
|
|
|
| |
(cherry picked from commit c9d93b62b0cc559d1ed4326212b6385cae2eb398)
|
|
|
|
|
| |
I should stop trying bad stuff, there seem to be so many holes to find in the validation :)
(cherry picked from commit 89ac71d38a4c49e1537e4afe2b34b2457d9817a7)
|
|\ |
|
| | |
|
|/
|
|
|
| |
Not sure what was the idea here, but these are not used anywhere, do nothing as they immediately call ```return false;``` plus the second one is also misnamed.
(cherry picked from commit edba33b5a567ab8c9d4827fa26a25bd9649e3fac)
|
| |
|
|
|
|
| |
(cherry picked from commit 1bbdab13e436f5f2b9e381886be4d9c2d1a4e44f)
|
| |
|
|
|
|
| |
(cherry picked from commit 153c3aa61fe65c51d584a57c032a4805048e3062)
|
|
|
|
|
|
|
|
| |
* rename function args to be clearer what they do ($local_only was quite ambiguous, at first sight it could mean any of: "don't update local catalog copy", "only check local catalog copy", or "only report local installed pkgs")
* merge nested if () conditions
* refactor minor code stuff
* rewrite explanatory comment
(cherry picked from commit 04daf8b1f016e17bede4ad00db46f2855d3e7c1f)
|
|
|
|
| |
(cherry picked from commit 2f633b526075b2ed5e0e160ef6f0d025b509bd70)
|
|
|
|
| |
(cherry picked from commit e5f96a2cb3c0cad0c828148bd7b8d45c130a9b17)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(resubmit)
Resubmit of PR #3157 with fix.
The issue in #3157 was that `pkg info` and `pkg search`, undocumented in man pages, seem to handle things differently if no packages match the pattern string. `pkg search` gives an error "No packages match [$pkgs]", whereas `pkg search` doesn't give an error.
I didn't come across this because it's not stated in the man pages for pkg info, and because I tested it with a bare install but at least one pkg, while @NYOB used it on a bare install.
The fix which I've tested and seems to work nicely, is to test using `pkg info -e` whether the pkg info call will hit a "no packages exist" issue or not. If `pkg info -e` returns 0 then it's safe as there's at least one matching pkg (any other errors are allowed to occur and be detected as usual). If it returns anything else, then there's no matching pkgs, so the main `pkg info` is skipped leaving $out and other variables at the correct values they need anyway, showing a null match/none found.
For details of the underlying issue being fixed, and the issue that this resubmit fixes, see the original PR.
(cherry picked from commit 587988f6df7e1d3b1a369b93a5634620129e3d9d)
|
|
|
|
| |
(cherry picked from commit 877be5e6205ada2608b364f57150010ba473e66d)
|
|
|
|
| |
(cherry picked from commit f2e58c16307795f572ff443e999c54eb6a9839e7)
|
|
|
|
| |
(cherry picked from commit 3e2028f4dca359e715058d2c35ae0df5b939657e)
|
|
|
|
| |
(cherry picked from commit fb572e810abe247c273c27ffafb129430b13be1f)
|
|
|
|
| |
(cherry picked from commit e52b5a409faa41222a4ff0c917355eb66d0ff19a)
|
|
|
|
| |
(cherry picked from commit 1095b20410963e748fe13268e6fa8f35ccce2319)
|
|
|
|
| |
(cherry picked from commit f311d3ba11572364488ee25ca9df08a33e42a089)
|
|
|
|
| |
(cherry picked from commit fe54f09154f4116ceea6897bff54a624f1eb63bc)
|
|
|
|
| |
(cherry picked from commit 8a1b5c561f93611b711eb4e7b58ccb4990577d8e)
|
|
|
|
| |
(cherry picked from commit c06865be6de6b164d06ee9bb1768dfe6829d783c)
|
|
|
|
| |
(cherry picked from commit 24b82516e0baac87316245427e870a36fbcda4ac)
|
|
|
|
| |
(cherry picked from commit c18d0d12b3e683f07b4bac933240332cd4d95829)
|
|
|
|
| |
(cherry picked from commit 950342400bdc75b35c01442c400bd53a18015818)
|
|
|
|
|
|
| |
configuration.
(cherry picked from commit 5a1d67b17d485697e19ef49d66e8e5f91e7e884d)
|
|
|
|
| |
(cherry picked from commit 01799e5bd5f363e21c744752760ab0cc591713da)
|
|
|
|
|
|
| |
When creating a new Captive Portal Zone the user can fail to select any of the Authorization Method radio buttons. No default radio button is selected - that is probably good, as the user has to think and click to decide which authorization method they will use.
But the form validation should check that some valid value is POSTed when the CP is enabled.
(cherry picked from commit 0ee22f364ca62b8305ff36447954dacdbc3c3cce)
|
|
|
|
|
| |
Add full stop and spacing between sentences.
(cherry picked from commit 0046a7da59fb3015512ce181cba6b37516c0b76f)
|
|
|
|
| |
(cherry picked from commit 2559f37539cf37221f8fddd7c0b7928e8e3969a8)
|
|
|
|
|
|
| |
Corrects malformed NMEA sentences by calculating and appending the checksum and adding missing special characters "$" and "*"
(cherry picked from commit 8c23d92a159c1282e7d185665977f0c45d45f845)
|
|
|
|
| |
(cherry picked from commit 4085eb055850e07540145c87fd6d3b5912a865dd)
|
|
|
|
|
|
| |
Note: is_intrange() only tells us that the range is good and might be delimited by a "-" or a ":", so if we want to take apart the 2 parts of the range (like is done here) we have to also test the string to decide which separator to use.
I decided it is fine to accept ranges with a ":" separator. Even though it is not explicitly mention on the UI, a user who accidentally does it will be pleasantly happy that it works.
(cherry picked from commit 71ff866c0b36c6a3e288e8bde02d0837fc0b73ce)
|
|
|
|
|
|
| |
Tags must be in the range 1 to 4094
Flag the various input errors and only report them once each.
(cherry picked from commit e0b7a2e76bddd121bc7f92a6ecb20266c8485ed1)
|
|
|
|
|
|
|
|
| |
1) Make the row delete button actually work
2) Do not allow ranges that go backwards like 25-20 or just "-" or 1-sided ranges "-42" "42-"
3) Remember the POSTed stuff to redisplay to the user if there were input errors
4) Ranges or numbers entered could overlap - just save a list of the unique members. e.g. If the user enters 5-15 and 10-20
(cherry picked from commit 477d849bd4e85af8bb3595eaf39f946de51d7289)
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Add GitSync options selectors to post update GitSync.
Minimal, Diff, Verbose, Dry Run
The GitSync options have utility for post update sync also.
|
| |
| |
| |
| |
| | |
Copy-paste error from code that used $_REQUEST. This is more correct to use $_POST.
(cherry picked from commit b07adc116c47a2f6a27ae69c84fe0e36a5a27fbd)
|