From admin at beckspaced.com  Mon Oct  5 06:17:21 2026
From: admin at beckspaced.com (Admin Beckspaced)
Date: Mon, 5 Oct 2026 08:17:21 +0200
Subject: [horde] FRAMEWORK_6_0 update: Horde\\Core\\Config\\MotdLoader
 class does not exist
In-Reply-To: <20261004141846.Horde.qr-Exe9z4-ZLZq5Oba52vQB@192.168.6.10>
References: <53a44fd2-e5d6-47a8-85c2-2f079edb83bb@beckspaced.com>
 <20261004074418.Horde.Myeq_mNIYyInbUD_IVVxuky@192.168.6.10>
 <20261004141846.Horde.qr-Exe9z4-ZLZq5Oba52vQB@192.168.6.10>
Message-ID: <760be2e6-b46e-4acf-83ee-b727d9886948@beckspaced.com>

Am 05.10.2026 um 00:18 schrieb Mike:
>
> Quoting Mike <barjunk at attglobal.net>:
>
>> Quoting Admin Beckspaced <admin at beckspaced.com>:
>>
>>> Hello there,
>>>
>>> I am seeing a reproducible error after updating Horde from the 
>>> FRAMEWORK_6_0 branch.
>>>
>>> Environment:
>>>
>>> openSUSE Leap 16.0
>>> PHP 8.4.24 (NTS)
>>> Apache 2.4.66 (Linux/SUSE)
>>>
>>> Known-working state:
>>>
>>> horde/horde: dev-FRAMEWORK_6_0 9b4c208
>>>
>>> Horde works normally in this state. I tested the login, Horde 
>>> administration and IMP, including successfully sending an email.
>>>
>>> Running:
>>>
>>> composer update
>>>
>>> currently performs exactly these three updates:
>>>
>>> horde/horde: dev-FRAMEWORK_6_0 9b4c208 → dev-FRAMEWORK_6_0 8a624b7
>>> horde/imp: dev-FRAMEWORK_6_0 3852464 → dev-FRAMEWORK_6_0 3a07a96
>>> horde/yaml: v3.0.1 → v3.0.2
>>>
>>
>> From github, it looks to me that Core needs to be at:
>>
>> 1b86e3c04b35863326c26fb9058233249a7ccb66
>>
>> or
>>
>> 1b86e3c
>>
>> That is where that class file lives currently as far as I can tell.
>
> This worked for me using Horde minimum-stability = stable
>
> Then
>
> composer require 
> horde/core=dev-FRAMEWORK_6_0#1b86e3c04b35863326c26fb9058233249a7ccb66
>
> Mike
>
Hi Mike,

thank you very much for your help. Your suggestion fixed the issue.

My installation was using horde/core v3.3.0. I changed Core as you 
suggested:

composer require 
'horde/core=dev-FRAMEWORK_6_0#1b86e3c04b35863326c26fb9058233249a7ccb66'

This upgraded horde/core from v3.3.0 to dev-FRAMEWORK_6_0 1b86e3c.

I first tested Horde with the new Core and the previously working 
horde/horde version. Login, IMP, sending mail and logout all worked 
without any problems.

I then ran a normal composer update, which updated:

horde/horde: dev-FRAMEWORK_6_0 9b4c208 -> dev-FRAMEWORK_6_0 f851ea4
horde/imp: dev-FRAMEWORK_6_0 3852464 -> dev-FRAMEWORK_6_0 3a07a96
horde/yaml: v3.0.1 -> v3.0.2

horde/core remained at dev-FRAMEWORK_6_0 1b86e3c as explicitly required.

I tested Horde again afterwards in a fresh private browser session: 
login, IMP, sending mail and logout all work correctly. The MotdLoader 
error is gone.

One additional observation regarding the dependency:

My installation is based on the official horde/bundle repository 
(https://github.com/horde/bundle.git). In the original bundle 
composer.json, horde/core is not a direct requirement. It was therefore 
installed as a transitive dependency and remained at the stable v3.3.0 
during my original composer update.

The newer FRAMEWORK_6_0 horde/horde code already uses 
Horde\Core\Config\MotdLoader, but Composer still considered horde/core 
v3.3.0 a valid dependency. This resulted in the combination where the 
new horde/horde code expected MotdLoader while the installed Core did 
not contain that class.

So I wonder if the dependency requirements in FRAMEWORK_6_0 need to be 
adjusted so that Composer automatically pulls in a sufficiently recent 
horde/core version when updating horde/horde.

In any case, explicitly requiring the FRAMEWORK_6_0 Core commit solved 
the problem here.

Thanks again for pointing me in the right direction!

Best regards
Becki