Skip to content
This repository was archived by the owner on May 29, 2026. It is now read-only.

fix: use force:false in repair step to prevent overwriting operator schema customisations#281

Merged
rubenvdlinde merged 1 commit into
mainfrom
fix/repair-force-false-template-c1
May 27, 2026
Merged

fix: use force:false in repair step to prevent overwriting operator schema customisations#281
rubenvdlinde merged 1 commit into
mainfrom
fix/repair-force-false-template-c1

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Summary

Fixes the loadConfiguration(force: true) anti-pattern in the Nextcloud repair step that was inherited from the app template scaffold.

  • Changes lib/Repair/InitializeSettings.php from force: true to force: false
  • Leaves SettingsController::load() on force: true (intentional admin reset button)

Why

force: true caused the seed register to be re-imported on every Nextcloud upgrade, silently overwriting any operator-customised schema fields, properties, and permissions.

force: false seeds only when not yet imported — the correct behaviour for an automatic repair step.

Closes #280

References

…chema customisations

The repair step's loadConfiguration(force:true) caused seed data to be
re-imported on every Nextcloud upgrade, silently overwriting operator-
customised schema fields, properties, and permissions.

force:true is intentional only on SettingsController::load() (manual
admin reset). The repair step should seed only when not yet imported.

Source: nextcloud-app-template C1 propagation sweep 2026-05-27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

1 participant