Skip to content

Lws49/feat marketplace pr7 versioning - #8523

Closed
LWS49 wants to merge 10 commits into
lws49/feat-marketplace-pr6d-auditfrom
lws49/feat-marketplace-pr7-versioning
Closed

Lws49/feat marketplace pr7 versioning#8523
LWS49 wants to merge 10 commits into
lws49/feat-marketplace-pr6d-auditfrom
lws49/feat-marketplace-pr7-versioning

Conversation

@LWS49

@LWS49 LWS49 commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

LWS49 added 10 commits July 29, 2026 17:30
A version IS its publication datetime, and the snapshot it serves is duplicated
into a `preview` container course so a published version can never change under
the courses that adopted it. Non-admins cannot edit container content.
Deleting the source assessment now orphans the listing instead of destroying it:
the marketplace keeps serving the snapshot, and the authoring copy is rebuilt in
the container automatically so a new version can still be published.
Browse, listing/question preview and duplication all read the current version's
snapshot rather than the live source assessment, and a manager can cut a new
version from the assessment page.
The banner dates both content vintages rather than numbering them, and cannot be
dismissed or muted: it is a statement of fact about the copy, so it stands until
the copy is updated or deleted. It offers the in-place update only while no
student has submitted; once one has, it explains why no action is possible.
One table of every listing across instances, with its version history, adoption
list, source provenance and the actions only an admin has: unlist, re-list,
rebuild the authoring copy, and permanently delete an unlisted listing.
Inside the preview container every listing's snapshots share one title, so the
index chip dates each one and links it to the listing it belongs to.
@LWS49

LWS49 commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator Author

Superseded by the 3-PR split of this work:

Closing in favour of those.

@LWS49 LWS49 closed this Jul 29, 2026
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.

1 participant