Missing people
People a family is looking for — searched by name and town, reported by families and read before they are shown, with the source of every record and the family's consent before a picture is published.
Everything below is declared by Missing people itself, so it describes this deployment rather than a manual — and it is rewritten whenever the program changes.
What it is
- Its key is MissingPeople, which is also the prefix of every component it owns.
- It is bought: a site has it only when the registry records that this customer bought it.
What it may be allowed to do
These are the permissions it declares. A person sees one of its screens only where his role carries the matching permission.
- missing.manage
- missing.moderate
- missing.setup
- missing.tips
- missing.view
What it puts on a page
3 components, each of which can be dropped onto a page in the composer.
Missing people
The people being looked for — searched by name, town, status and year.
Placed as MissingPeople.List.
5 settings:
- How many on a page — a number, left alone it is 24.
- How many across — a number, left alone it is 4.
- Show the search and filters — a switch, left alone it is true.
- Only people still missing — a switch, left alone it is false.
- Pages — chosen from No pages, Under the list, Above and under, left alone it is below.
Missing person's page
One person in full, reached by its address, with a private form for what visitors know.
Placed as MissingPeople.Detail.
2 settings:
- Say where the record came from — a switch, left alone it is true.
- Show the form for what visitors know — a switch, left alone it is true.
Report a missing person
The form a family sends a report with. Every report is read before it is shown.
Placed as MissingPeople.Report.
It takes no settings — it draws one way and has nothing to be told.
Comments
Nobody has written yet. Be the first.
This article is not taking comments.