Export carries binned wiki pages, and import puts them straight into the bin (Q134 / X1) #1009

Closed
opened 2026-10-01 20:38:01 +00:00 by claude-bot · 2 comments
Collaborator

The owner's answer to Q134 (X1), 2026-10-01: (b), over the recommendation. To be recorded as D262.

What was built (#998, for #990): what is in the bin stays out of the export file, so an import can never bring a binned page back as a live page players can read.

What changes: a binned wiki page travels in the export, marked as binned with the time it was binned, and an import puts it straight into the bin: GM-only, never readable or searchable by a player, until a GM restores it. The bin's 30 days carry across the move (the original binned time is kept, so the clock does not restart).

Must hold:

  • An imported binned page is never live at any point, including if the import fails half way.
  • Everything that hangs off a binned page (its sections, files, links, sheet, quest details, reveals) comes back in the state a binned page's dependants have on the source server, and nothing about it reaches a player.
  • An older file (schema before this change) imports as before.
  • An older server refuses the newer file by its schema version, as today.
  • The ledger in tests/export/test_export_bin.py is updated with true reasons. Other binned things (transcripts, audio, campaigns) are not part of this change.

Export schema version bump, tests, docs/ for the export format, changelog fragment.

**The owner's answer to Q134 (X1), 2026-10-01: (b)**, over the recommendation. To be recorded as D262. **What was built (#998, for #990):** what is in the bin stays out of the export file, so an import can never bring a binned page back as a live page players can read. **What changes:** a binned wiki page travels in the export, marked as binned with the time it was binned, and an import puts it **straight into the bin**: GM-only, never readable or searchable by a player, until a GM restores it. The bin's 30 days carry across the move (the original binned time is kept, so the clock does not restart). **Must hold:** - An imported binned page is never live at any point, including if the import fails half way. - Everything that hangs off a binned page (its sections, files, links, sheet, quest details, reveals) comes back in the state a binned page's dependants have on the source server, and nothing about it reaches a player. - An older file (schema before this change) imports as before. - An older server refuses the newer file by its schema version, as today. - The ledger in `tests/export/test_export_bin.py` is updated with true reasons. Other binned things (transcripts, audio, campaigns) are not part of this change. Export schema version bump, tests, `docs/` for the export format, changelog fragment.
Author
Collaborator

Done in PR #1016, merged to main on 2026-10-02 once its CI re-run went green.

Export schema is now 16: binned wiki pages travel in a GM-only wiki_bin section (never in lore_entries, never under wiki/), and an import inserts them already binned, in the same transaction as the live pages. Older files import as before; a wiki_bin in a file claiming schema 15 or lower is ignored. No migration. Recorded as D262; the full behaviour and tests are in the PR body.

Before merging I checked the branch against current main: it merged cleanly and main had changed no export, import or archive file since the branch last took main, so the green run still describes what landed.

Done in PR #1016, merged to main on 2026-10-02 once its CI re-run went green. Export schema is now 16: binned wiki pages travel in a GM-only `wiki_bin` section (never in `lore_entries`, never under `wiki/`), and an import inserts them already binned, in the same transaction as the live pages. Older files import as before; a `wiki_bin` in a file claiming schema 15 or lower is ignored. No migration. Recorded as D262; the full behaviour and tests are in the PR body. Before merging I checked the branch against current main: it merged cleanly and main had changed no export, import or archive file since the branch last took main, so the green run still describes what landed.
Author
Collaborator

Owner's answer to Q142 (X4), 2026-10-03: (a), as recommended. An imported binned page whose 30 days are already up gets a week from the day it arrives. A page that still has time left keeps its original day.

As merged in #1016, an overdue page would go at the next nightly clean-up, possibly minutes after the import. The follow-up is being built now (to be recorded as D270), under a new issue linked here.

**Owner's answer to Q142 (X4), 2026-10-03: (a), as recommended.** An imported binned page whose 30 days are already up gets **a week from the day it arrives**. A page that still has time left keeps its original day. As merged in #1016, an overdue page would go at the next nightly clean-up, possibly minutes after the import. The follow-up is being built now (to be recorded as D270), under a new issue linked here.
Sign in to join this conversation.
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
rbrooks/Quest-Board#1009
No description provided.