﻿id,summary,reporter,owner,description,type,status,priority,mile
stone,component,version,severity,resolution,keywords,cc,focuses
18822,get_permalink() produces an add. DB request without
$post->filter,F J Kaiser,ryan,"When used in a Query-Loop,
`get_permalink()` makes an additional query `$post =
&get_post($id);` to produce a valid link to the post (in
example: archive pages). This means that you'll get one
additional query ''per'' post-permalink on your archive page,
which can pretty fast sum up. When looking at
[http://core.trac.wordpress.org/browser/trunk/wp-includes/link-
template.php?annotate=blame&rev=18328#L95 link-template.php line
95], you can see the `if`/`else` statement that avoids throwing
a complete `$post` object into the function to produce a
permalink without an additional query. ''The exact line that
prevents using the post object:'' {{{ if ( is_object($id) &&
isset($id->filter) && 'sample' == $id->filter ) { }}} So far the
only possible solutions that can prevent that behaviour are
shown in t