#3542 closed New feature (fixed)
Allow month-based date_list on archive_index
Reported by: | anonymous | Owned by: | David Tulig |
---|---|---|---|
Component: | Generic views | Version: | dev |
Severity: | Normal | Keywords: | date_list month generic view |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
I was trying to create a blog index, similar to the Django weblog, which has a Month and Year archive sidebar.
I figured the correct thing to use was the archive_index generic view, but the date list only gives me years.
I can almost see the reason for this, as archive_index would drill down to archive_year, but it's rare that you would list the years first except for very long-running blogs.
I propose a new argument to archive_index of "date_list_period" which can be 'year' (default) or 'month'.
Attachments (3)
Change History (20)
comment:1 by , 18 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 17 years ago
Triage Stage: | Design decision needed → Accepted |
---|
comment:3 by , 17 years ago
Has patch: | set |
---|---|
Keywords: | sprintdec01 added |
Owner: | changed from | to
by , 17 years ago
Attachment: | date_list_period.diff added |
---|
comment:4 by , 17 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
comment:5 by , 17 years ago
Attaching an updated revision of the patch that appplies to trunk as of r7354.
by , 17 years ago
Attachment: | t3542-r7354.diff added |
---|
comment:6 by , 16 years ago
milestone: | → post-1.0 |
---|
by , 16 years ago
Attachment: | 3542-month-based-archive_index-generic-view-r9973.diff added |
---|
Updated patch to trunk after the documentation refactoring
comment:8 by , 16 years ago
Keywords: | month generic view added; sprintdec01 removed |
---|
comment:9 by , 14 years ago
Patch needs improvement: | set |
---|---|
Triage Stage: | Ready for checkin → Accepted |
Hold on a bit... if I have data from multiple years in my database, isn't this going to collapse *all* the January months into one? That's considered useful?!
The documentation is a little confusing to me. It's correct, but doesn't really tell me *what* a year or month year does. Could we put in a little example of what the output of each might look like so that a user knows why they might want one or the other option?
comment:11 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → New feature |
comment:14 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:16 by , 12 years ago
This commit could have used more docs... I'm taking care of them now...
Adds the new parameter and documentation.