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
* Port license page to MVC
* Use more template variables on the license page.
Also make sure to handle cases where someone changes one of the variables (e.g. when creating their own product based on OPNsense). Discussed with Jos Schellevis.
* Move legacy menu to Core
* Use another approach to display ®
* ACL fix
So lease time is in UTC, avoid using GMT for clarity.
Append UTC to UTC time when displayed. We just need to either
take the time as is or move it from UTC to local if option set.
It's very difficule to improve UX of this page. We now have a
separate changelog tab which helps with clarity over what is
"updated".
Now we can always go back to the last log of the past action.
And the log will not jump from the old content to the new one
when an action starts.
Two problems remain: the transition during "check for update"
looks quite empty. And there is no user guidance as to where
he is and what he is will install in an overview shape.
which makes this precaution a complication as unbound disables
IPv6 responses with it as well and we shouldn't set prefer-ip6
to 'yes' to avoid further breakage.
PR: https://forum.opnsense.org/index.php?topic=10810.0
