Skip to content

fix(timeobjects): skip missing optional drivers without error spam#2

Merged
ralflang merged 1 commit into
FRAMEWORK_6_0from
fix/timeobjects-skip-missing-optional-drivers
Jul 21, 2026
Merged

fix(timeobjects): skip missing optional drivers without error spam#2
ralflang merged 1 commit into
FRAMEWORK_6_0from
fix/timeobjects-skip-missing-optional-drivers

Conversation

@TDannhauer

Copy link
Copy Markdown
Contributor

Summary

  • Stop logging errors when optional TimeObjects drivers (Weather, FacebookEvents) are not installed.
  • Missing Horde_Service_Weather / Horde_Service_Facebook is treated as a normal skip during category discovery.

Motivation

After the PSR-3 logger wiring, every calendar/category probe logged:
TimeObjects driver "Weather|FacebookEvents" failed to initialize: … is not installed
when those suggest packages were absent (and conf already disables them). That is expected, not a failure.

Changes

  • listTimeObjectCategories() checks class_exists() for each driver’s required service class and continues without logging when absent.
  • Real initialization failures after a package is present still log at error level.

Test plan

  • Without horde/service_weather / horde/service_facebook installed, open Kronolith (or any UI that lists time object categories) and confirm /tmp-horde/horde.log no longer gets the “is not installed” errors.
  • With weather configured and the package installed, Weather still appears as a time object category when ensure() succeeds.

Weather and FacebookEvents depend on Composer suggest packages. When
those are not installed, listTimeObjectCategories now skips them
quietly instead of logging an error on every category probe.
@TDannhauer
TDannhauer requested a review from ralflang July 20, 2026 05:39
@ralflang
ralflang merged commit f97f9b8 into FRAMEWORK_6_0 Jul 21, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants