Skip to content

fix(admin/theme): remove duplicate <la:errors> rendering on theme list page#3179

Merged
marevol merged 1 commit into
masterfrom
fix/admin-theme-duplicate-errors
Jul 1, 2026
Merged

fix(admin/theme): remove duplicate <la:errors> rendering on theme list page#3179
marevol merged 1 commit into
masterfrom
fix/admin-theme-duplicate-errors

Conversation

@marevol

@marevol marevol commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Problem

On the theme admin list page (admin_theme.jsp), the message block rendered a bare <la:errors/> and two property-specific tags:

<la:errors/>
<la:errors property="_global"/>
<la:errors property="name"/>

A bare <la:errors/> already outputs the errors of every property, so any global action error (for example a failed theme reload or a theme-not-found error, which AdminThemeAction registers under the global property) was rendered twice on the screen.

In addition, <la:errors property="name"/> was dead code: the theme list flow never registers errors under the name property (ThemeListForm only has a defaultTheme field).

This is the only admin page that combined a bare <la:errors/> with property-specific <la:errors> tags in the same block; all sibling list pages use a single bare <la:errors/>.

Fix

Keep only the bare <la:errors/>, removing the two redundant property-specific tags. Every error is now displayed exactly once, and no error is dropped (the bare tag still covers _global as well as field errors such as defaultTheme). This matches the other admin list pages (dict, backup, maintenance, plugin, storage, log).

How to reproduce

Trigger any global error on the theme list page (e.g. a theme reload failure). Before the fix the message appears twice; after the fix it appears once.

…t page

The theme admin list page rendered a bare <la:errors/> together with
<la:errors property="_global"/> and <la:errors property="name"/> in the
same message block. Because a bare <la:errors/> already outputs errors
for every property, any global action error (for example a failed theme
reload or a theme-not-found error) was shown twice. The property="name"
tag was also dead code, since the list flow never registers errors under
the "name" property.

Keep only the bare <la:errors/> so each error is displayed exactly once,
consistent with the other admin list pages (dict, backup, maintenance,
plugin, storage, log).
@marevol marevol self-assigned this Jul 1, 2026
@marevol marevol added the bug label Jul 1, 2026
@marevol marevol added this to the 15.8.0 milestone Jul 1, 2026
@marevol marevol merged commit 2649379 into master Jul 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant