fix: update feed emits string client values instead of numeric 0/1 #602

New Issue

2026-06-11T21:15:18Z

jmiller commented

2026-06-11 21:15:18 +00:00

Problem

The Joomla update XML feed emits <client>site</client> and <client>administrator</client> as string values. Joomla's Update.php casts <client> to int, so both strings cast to 0 (site). Admin extensions get misidentified as site-side.

Expected

<client>0</client>  <!-- site -->
<client>1</client>  <!-- administrator -->

Current

<client>site</client>        <!-- casts to 0, accidentally correct -->
<client>administrator</client>  <!-- casts to 0, WRONG for admin extensions -->

Fix

In services/updateserver/joomla.go lines 386-389, change string values to numeric:

client := "0" // site
switch extType {
case "package", "component", "library", "file":
    client = "1" // administrator
}

Impact

All admin-side Joomla extensions (packages, components, libraries, files) served via MokoGitea update feeds have incorrect client values. Joomla may fail to match updates for these extensions.

## Problem The Joomla update XML feed emits `<client>site</client>` and `<client>administrator</client>` as string values. Joomla's `Update.php` casts `<client>` to int, so both strings cast to `0` (site). Admin extensions get misidentified as site-side. ## Expected ```xml <client>0</client>  <client>1</client>  ``` ## Current ```xml <client>site</client>  <client>administrator</client>  ``` ## Fix In `services/updateserver/joomla.go` lines 386-389, change string values to numeric: ```go client := "0" // site switch extType { case "package", "component", "library", "file": client = "1" // administrator } ``` ## Impact All admin-side Joomla extensions (packages, components, libraries, files) served via MokoGitea update feeds have incorrect client values. Joomla may fail to match updates for these extensions.

~~jmiller referenced this issue 2026-06-11 21:16:36 +00:00~~

fix: update server feed generation bugs in joomla.go #601

jmiller commented

2026-06-11 21:16:48 +00:00