| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The blue "set as global config" button was too tempting to click after
creating or editing a system config. Accidentally setting location
specific config as globally active easily happened.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #3336
|
|
|
|
| |
references #3313
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
direction too
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This fixes #3121
|
| |
|
|
|
|
|
| |
this should clarify that you can cancel this step (in case the user
uploaded a non-svg). The lonely "save" button was causing some confusion...
|
|
|
|
| |
no cert is supplied
|
| |
|
|
|
|
| |
homeattr scan info
|
| |
|
| |
|
| |
|
|
|
|
| |
a config
|
|\ |
|
| | |
|
|/
|
|
| |
get rid of JS hack for ellipsis in tables (by adding a HTML/CSS hack for it :))
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
improve config module handling
|
| |
|
| |
|
| |
|
|
|