The initial design of the options could have been better. Too
much smarts for little benefit. Break "All" interface option
while here, we shouldn't use a text that could be an interface.
Also, remove the table widget layout fix since we have text-wrap.
But ironically enough Firefox doesn't care about text-wrap so
we are back to overflowing the container on long words.
It's still the same issue: too little space for displaying what
you want to display. I'm not going to work on this anymore.
* Use rcorder to correctly order the startup sequence, which
will avoid further workarounds in plugins.
* Defer the execution of /etc/rc.d/ipfw due to bug #2569,
while also removing the previous non-functional workaround.
* add ui logic for certificate selection
* add local_port
* extend model, which should be used to remember the previous selection and conveniently adds form validation features
* add validatePresetsAction() and storePresetsAction() which can be used to store and validate presets, used in downloadAction() action to persist choices
* gather needed data to generate client config in downloadAction(), todo: add certificate content
* Add factory class to request export template types
* Add some test code to show/hide options depending on supported functions
* Use our normal form type to construct the UI
* Use stored ip/hostname when available or determine target based on ip address, the previous hostname resolution type will be replaced.
* List configured templates using /api/openvpn/export/templates/
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 › »`).
