Cockpit UI - validation messages

Bug
,
1

Minor/cosmetic bugs.
From Cockpit (System -> Trusted Netwoks -> Add Network):
1)

The validation message suggest something like ‘10.0.0.1’ (an IP address) instead of a network address. Using an IP address the settings cannot be saved and no validation message warns about the error:
cockpit%20trusted%20networks%20-%20cannot%20save%20network%20address%20set%20as%20suggested

Firewall objects. Missing strings for validation messages:
cockpit-firewall-objects-hosts-missing-validation-strings cockpit-firewall-objects-host-group cockpit-firewall-objects-cidr-valid-cidr-block cockpit-firewall-objects-time-condition-validation-messages

Firewall object services: some of the listed protocols cannot be used:
cockpit-firewall-objects-services1
Also the service name can be anything. For instance, setting an space as name the service is saved but cannot be deleted.
Bug or feature? a service object with same port numbers as an existing one can be created.

Firewall -> Port Forward:
cockpit-firewall-port-forward-port-validation
Also on port forward, allowed external public IPs (one per line) field is not validated.

nethserver-dc (create user/group) missing strings:
AD%20create%20user%20-%20valid%20username

Note: This was tested with stable versions.

Cockpit packages from testing are not ready for use (blank pages on terminal and applications):

nethserver-base.noarch 0:3.7.3-1.3.g19916a8.ns7                               
nethserver-cockpit.noarch 0:1.1.2-1.2.gcfe40f9.ns7                            
nethserver-cockpit-lib.noarch 0:1.1.2-1.2.gcfe40f9.ns7
2 Likes
2

I’d like to add another not so cosmetic bug : when clicking on “Open” buttons in the Applications tab, the link should follow the virtualhost used to customise the links to access the apps like nextcloud and Sogo’s VirtualHost config key or Webtop’s PublicUrl key.

1 Like
3

Certificates seems to have some other missing validation strings messages:

4

Issue opened: Cockpit: add missing validation labels · Issue #5884 · NethServer/dev · GitHub

It should be already as you described, at least for all applications which implement the API.
I don’t know about SOGo, but nextcloud and mattermost should already have the described behavior.

Could you please open a separate topic if the problem persists?

5

You can check the new translation messages here: https://github.com/NethServer/dev/issues/5884

3 Likes
6

Tested and verified !

3 Likes