This reverts commit d60b154b0ccd25aafd861b57e4898227b03da286.
The normal theme menu does not use separators so the sidebar
shouldn't use them as well. Noticed this morning with a fresh
pot of coffee.
Most of this will only be relevant for 19.1 where we shall have
an "enforcement" of mtree files through the sets so that this
check can audit our whole system for issues... :)
I noticed that the separation of the individual <a> links is missing. Now it is up to you to say if we should install it again or not. if you do not want it please just delete this pr. have added two screenshots as a comparison. Thank you, best regards, René
Currently, pagination uses double guillemets for first/last page and lower than/greater than signs for previous next (like so: `« < 1 2 3 > »`). Change this to use single guillemets, for visual consistency (like so: `« ‹ 1 2 3 › »`).
The legacy code populated a list of users and certificates, where the user only seems to be used to prefix some content and filter on server type, it seems more obvious to just export related certs for the requested server and show which users it connects to.
When using toArray() on a config, it would try to detect sequential items by reading all keys using isArraySequential(), this may cost a lot of time (seconds) if the config
contains a lot of items. Found when testing Sensei.
This change doesn't impact mvc style components.
This allows us to call a funcion which will generate the correct
credentials where they need to be hashed or not. In the function
in this PR, the function returns all of the request and send
options required for Orange France and fills in the client fields
automatically.
Also in the case of Orange France an extra entry box appears to
allow the entry of the LiveBox_ID.
The PR is a work in progress, but all that is needed to make it
work for Orange France is the hash routine.
It's also possible to use the functions create the hex strings
needed for other ISPs and auto fill the options as needed.
-- /api/firewall/alias_util/add/[alias]
-- /api/firewall/alias_util/delete/[alias]
both accepting address as parameter, sample usage added to the pfTables diagnostic page
