mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-11-20 15:10:05 +00:00
The host status popover, the save warning, the modal error and the error toasts showed the backend's English message (nginx_err / error.message) in every language, e.g. 'Advanced configuration: unknown directive "proxy_passs" (line 3).', 'Nginx rejected Proxy Host #3: ...', 'Disabled automatically: ...' and the hints. Backend: NginxConfigError.details (and so meta.nginx_details) now also say what the UI words the message from: `area` + `relative_line` (where in the host's config, host_advanced), `reason` for the special cases (conflict, regenerated_conflict, too_many_broken_hosts with `max`, redacted), `detail` (the humanised nginx error on its own), `hint_code` (the rule of the hint), `auto_disabled` in the meta of a host taken offline while another host was saved, `context: "default_site"`. An unsafe_value offline meta names the value in `field` (eg. forward_host, from unsafeValueError()'s new optional argument) and carries the value itself, quoted, as `detail`. The English message stays as it was for API users and logs. Schema, docs and unit tests cover the new fields. Frontend: describeNginxError() words the error from these details in the UI language (nginx-error.*, en/de/et/vi), nginx's error is shown below it untranslated, the hint comes from nginx-error.hint.<code>. Used by the host status popover, SaveWarning, NginxErrorMessage and formatApiError() (one line for toasts). Details stored by an older version keep showing the backend's message. An unsafe value is shown after the name of its field (the form's label where one exists, nginx-error.field.* otherwise). The status badge of a disabled host uses the existing `disabled` text, which more languages translate, instead of a new host-status.disabled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .vitepress | ||
| scripts | ||
| src | ||
| .gitignore | ||
| package.json | ||
| yarn.lock | ||