Opened 17 years ago
Closed 11 years ago
#10180 closed enhancement (wontfix)
Add rel="prev" to previous_posts_link() and rel="next" to next_posts_link()
| Reported by: | singpolyma | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Posts, Post Types | Version: | |
| Severity: | normal | Keywords: | has-patch needs-testing |
| Cc: | Focuses: | template |
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
http://gist.github.com/120586
Really this should (IMHO) all go into core
Attachments (1)
Change History (15)
#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.
#8
@
17 years ago
- Resolution duplicate
- Status closed → reopened
- Summary rel=prev/next → 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
@
17 years ago
This needs to hit similar functions such as previous_image_link() and next_image_link()
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
What version is this patch against?
See: http://core.trac.wordpress.org/ticket/8703