Features/hide version

[Orgenus]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?

---

Add hide_version Option to WebUI Branding Config

Summary

Adds a new hide_version boolean field to the UIBranding configuration that allows operators to hide the application version string from the WebUI footer entirely — including the footer container itself.

---

Problem

The application version was always visible in the footer of both the WebAdmin and WebClient interfaces with no way to suppress it via configuration. This can be undesirable in production deployments where operators prefer not to expose internal version information.

---

Solution

Added a hide_version field to the UIBranding struct. When set to true, the entire #kt_app_footer element is omitted from the rendered HTML — not just the version text, but the footer container as well.

The setting is independently configurable per interface (web_admin and web_client).

---

Configuration

"branding": {
    "web_admin": {
        "hide_version": true
    },
    "web_client": {
        "hide_version": true
    }
}

No restart of the OS process is required beyond the normal config reload — a service restart is needed for the changes to take effect.

---

Files Changed

File	Change
internal/httpd/httpd.go	Added HideVersion bool to UIBranding struct with JSON/mapstructure tags
internal/httpd/web.go	Added HideVersion bool to commonBasePage struct
internal/httpd/webadmin.go	getBasePageData: reads HideVersion from admin branding and sets it on the base page
internal/httpd/webclient.go	getBaseClientPageData: reads HideVersion from client branding and sets it on the base page
templates/common/base.html	Footer block wrapped with {{if and .LoggedUser.Username (not .HideVersion)}} — entire #kt_app_footer div is suppressed when enabled

---

Notes

• The HideVersion flag does not affect the defaultVersion used for i18next cache-busting in the <script> block — only the visible footer element is affected.
• Since commonBasePage is embedded in all page structs (both admin and client), the field propagates automatically to every rendered page without additional changes.