bug: update server feeds still respond when feature is disabled #589
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The update server endpoints (
/updates.xml,/updates/dolibarr.json, etc.) still respond with valid feed data even when the update server feature is disabled for a repo.PR #579 fixed the settings persistence side (deleting the repo config row when the toggle is unchecked), but the
RepoAssignmentPublicFeedmiddleware inservices/context/repo_public_feed.godoes not check whetherLicensingEnabledis true. When no repo config exists, it defaults to platform"joomla"and allows the request through.Expected Behavior
When the update server is disabled (no repo-level config with
LicensingEnabled=trueAND no org-level config withLicensingEnabled=true), the feed endpoints should return 404.Fix
The
RepoAssignmentPublicFeedmiddleware needs to checkLicensingEnabledon both the repo config and org config, returning 404 if neither has it enabled.Fix is on branch
chore/mcp-cleanup.Branch created:
feature/589-bug-update-server-feeds-still-respond-wh