Migrate existing v0.1.0 installs on upgrade #39

New issue

Open

opened 2026-07-01 01:05:43 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 01:05:43 +00:00

(Migrated from github.com)

Problem

Sites upgrading from v0.1.0 need their options migrated to the new data-source defaults without breaking, and without losing user configuration.

Acceptance criteria

An upgrade routine runs once on version bump and sets new defaults (Api source) without clobbering existing rubric/calendar settings.
Existing pretty-page rewrite rules continue to resolve after upgrade.
The migration is idempotent and logged at debug level only.
readme.txt changelog documents the upgrade behaviour.

Notes

Default upgraded installs to Api source but preserve a working calendar throughout.

## Problem Sites upgrading from v0.1.0 need their options migrated to the new data-source defaults without breaking, and without losing user configuration. ## Acceptance criteria - [ ] An upgrade routine runs once on version bump and sets new defaults (Api source) without clobbering existing rubric/calendar settings. - [ ] Existing pretty-page rewrite rules continue to resolve after upgrade. - [ ] The migration is idempotent and logged at debug level only. - [ ] readme.txt changelog documents the upgrade behaviour. ## Notes Default upgraded installs to Api source but preserve a working calendar throughout.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Ordo#39

No description provided.

Rows
Columns