Just change the returned information into something that
makes sense here. No functional changes between both
sides except we check repository for != 'ok' so we catch
all types of errors if they are added in the future. Same
is already true for connection.
- remove locking in model, core framework should do that if required. (see Config->lock), deadlock issues in previous code (freezing UI)
- in settings controller, expand endpoints to one per type (in stead of "one to rule them all")
- in settings controller, align to base wrappers of ApiMutableModelControllerBase
- move extended validations to model, to avoid validation issues when another service would like to reuse the model
- align forms to standard wrappers (naming convention, simplifies code)
- remove "deleteRelations", if we need something like this at some point, it should be in the model, for now it seems safe enough to ditch
- ditch migration code, since it does the same as having a default value (defaults are always enforced during migrations)
** left UnitTest code for what it is now, probably needs changes too
include_once returns TRUE if the file has already been loaded. This is not what you want if you're setting a variable from it.
http://php.net/manual/en/function.include-once.php
This fixes notices when including certain old scripts from modern controllers, as well as a notice when running run_migrations.php.
Firmware has both reboot and poweroff (halt) for early API access reasons,
but since they are not in the best place start by migrating the cron hook.
I am not sure when we should remove the firmware hooks, maybe in 19.7...
* Stop mentioning how tokenizer fields work. Web proxy is the only
part where this is done excessively and best explained in docs.
* Remove "->" as it could lead to invalid characters in HTML and
translation misakes later on.
* Updated the help section for "Forwarded_for"
Updated the help section for "Forwarded_for", based on original Squid documentation at http://www.squid-cache.org/Doc/config/forwarded_for/
Other option could be to use lesser verbosity and use the squid documentation hyperlink in the help text, but this might make the help section sensitive for URL changes outside the OPNsense project itself.
* started removing <br> and markup language.
To be continued
* Removed allmost all formatting
Points for discussion is how to handle the URLs that refer to the templates that create Port forwarding and firewall rules for HTTP and HTTPs redirection
* Removed CDATA
