Opened 17 years ago
Closed 17 years ago
#5088 closed (invalid)
Small typo in the model name for flatpages under the admin interface
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Contrib apps | Version: | dev |
| Severity: | Keywords: | flatpages admin | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When django.contrib.flatpages is enabled, the model shows up under the admin interface as "Flat pages", rather than "Flatpages" as it should be, from what I can tell. A minor typo, so nothing major, but easily fixed as well.
Change History (2)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
The Python convention for class names is that multi-word names should be compressed using CamelCase -- "Flat page" becomes a class named "FlatPage". For ease on human eyes, the Django admin splits such names back out into multiple words -- e.g., a class "BlogEntry" would become "Blog entry" in the admin. This is documented under the verbose_name option for models.
Note:
See TracTickets
for help on using tickets.
Actually, which is correct? Flatpages or flat pages... both are used through the add-on itself, as well as the related documentation.
So, you probably can just ignore this ticket as I'm not really sure which is correct anymore.