Opened 17 years ago
Closed 10 years ago
#10180 closed enhancement (wontfix)
Add rel="prev" to previous_posts_link() and rel="next" to next_posts_link()
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Posts, Post Types | Keywords: | has-patch needs-testing |
| Focuses: | template | Cc: |
Description
Putting proper rel values on archive next/previous links is actually not even properly possible with a plugin, so I had to use a patch
Really this should (IMHO) all go into core
Attachments (1)
Change History (15)
#2
@
17 years ago
- Keywords close added
- Milestone changed from Unassigned to 2.8.1
this seems very invalid to me
#3
@
17 years ago
- Keywords close removed
#8703 added next/prev/home for single browsing, But not for archive browsing.
/archive/2009/05/ should have a next for /archives/2009/06/ etc.
I'm pretty sure thats what this ticket is asking for.
#4
@
17 years ago
- Keywords needs-patch added
- Milestone changed from 2.8.1 to 2.9
- Type changed from defect (bug) to enhancement
#8
@
17 years ago
- Resolution duplicate deleted
- Status changed from closed to reopened
- Summary changed from rel=prev/next to Add rel="prev" to previous_posts_link() and rel="next" to next_posts_link()
I guess I should really pay more attention to things. #4209 and this cover different things (previous_post_link() vs previous_posts_link() and the next equivalents). I'm reopening and I'll have a patch soon.
@
17 years ago
This is my first go at adding in the rel="next" and rel="prev". There is probably a better/faster way of doing this.
#10
@
16 years ago
This needs to hit similar functions such as previous_image_link() and next_image_link()
What version is this patch against?
See: http://core.trac.wordpress.org/ticket/8703