Make WordPress Core

Opened 21 years ago

Closed 19 years ago

#2352 closed enhancement (fixed)

Add ability to display yearly archives list

Reported by: stewart Owned by: westi
Priority: normal Milestone: 2.1
Component: Template Version: 2.0
Severity: normal Keywords: has-patch wp_get_archives yearly commit
Cc: Focuses:

Description

Wordpress has daily, weekly, and monthly archive types, but strangely no yearly type.

Attachments (4)

template-functions-general.php.diff​ (1.5 KB ) - added by stewart 21 years ago.
Patch to add yearly archive type
template-functions-general.php.updated.diff​ (1.4 KB ) - added by westi 21 years ago.
Improved patch using get_year_link
2352.diff​ (1.4 KB ) - added by westi 20 years ago.
This one really doesn't use $now
archives-yearly.diff​ (1018 bytes ) - added by snakefoot 19 years ago.
Patch for branch 2.0

Download all attachments as: .zip

Change History (12)

@stewart
21 years ago

Patch to add yearly archive type

@westi
21 years ago

Improved patch using get_year_link

#1 @westi
21 years ago

  • Component General → Template
  • Keywords bg|has-patch added
  • Milestone → 2.1
  • Owner changed from anonymous to westi
  • Severity normal → enhancement
  • Status new → assigned
  • Summary Yearly archives type → Add ability to display yearly archives list

I have updated the patch to use get_year_link instead of (get_settings('home') to ensure the archive links produced obey the current permalink rules.

I have also removed the MONTH(post_date) AS month from the query as it is not needed.

This looks good for 2.1 as it is an enhancement.

#2 @westi
21 years ago

  • Keywords bg|commit added

#3 @westi
20 years ago

Patch rebased against trunk for the bug hunt

#4 @ryan
20 years ago

Needs to be updated to remove the < $now stuff.

@westi
20 years ago

This one really doesn't use $now

#5 @ryan
20 years ago

  • Resolution → fixed
  • Status assigned → closed

(In [4138]) Add yearly archive display option. Props stewart and westi. fixes #2352

#6 @snakefoot
19 years ago

  • Milestone 2.1 → 2.0.eventually
  • Resolution fixed
  • Status closed → reopened

Could this be applied to the 2.0 branch ? Every time a security fix comes for 2.0, then I have to re-apply this as my blog isn't getting any younger.

@snakefoot
19 years ago

Patch for branch 2.0

#7 @ryan
19 years ago

  • Milestone 2.0.eventually → 2.1

2.0 is restricted to security fixes.

#8 @Nazgul
19 years ago

  • Keywords has-patch commit added; bg|has-patch bg|commit removed
  • Resolution → fixed
  • Status reopened → closed
Note: See TracTickets for help on using tickets.