Repository navigation
Experiences and plans in the admin - #180
Merged
Merged
Conversation
- Experience resource: fields, 16-language tabs, places with a position - Plan resource: curated and travellers' public plans only, stops by day - PlanPolicy: private plans never found, travellers' plans read-only - AdminAssociationGate: attaching and detaching ask the parent's policy - Shared translation tabs for places, experiences and plans - Brain: slice 4 build notes, the plans answer as a source
misabegovic
marked this pull request as ready for review
September 30, 2026 17:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Curators can now edit experiences and plans in the admin, with titles and descriptions in all 16 languages, the places an experience visits in order, and a plan's experiences and places by day.
The plans list holds curated plans and travellers' public plans only, as decided; a private plan is not found even by its link. A traveller's public plan is read-only, and only admins delete, and only curated plans. Avo links related records through its own controller, which the per-resource check did not reach, so that controller now asks the parent record's policy too: nothing can be attached to a traveller's plan. This is slice 4 of wiki/initiatives/avo-admin-and-roles.md.