bug in thematic_postfooter_postcategory()

[GoogleCodeExporter]

What steps will reproduce the problem?
1. View an individual post
2. Look at the 'entry-utility' div
3. Wonder why the '|' separator is not displayed

What is the expected output? What do you see instead?

You should see the '|' separator, as is shown in the 'entry-utility' div on the 
main index page:

Posted in Examples, Uncategorized | Leave a comment

Instead, you see this, with no separators:

This entry was posted in Examples, Uncategorized. Bookmark the permalink. Post 
a comment or leave a trackback: Trackback URL.

What version of the product are you using? On what operating system?
svn rev 751, Mac OS X

Please provide any additional information below.

The thematic_postfooter_postcategory() function in 
'library/extensions/content-extensions.php' (svn rev 751) has the <span 
class="meta-sep meta-sep-tag-links"> code in the wrong place.

As a result, the separator tag does not show up. To make it show up, the 
following line should probably be after the *end* of the if/then/else block 
instead of within it:

$postcategory .= '</span> <span class="meta-sep meta-sep-tag-links">|</span>';

Or, if meta-sep-tag-links is not supposed to be on this page, then delete the 
code entirely.

Original issue reported on code.google.com by moo...@gmail.com on 18 Nov 2010 at 3:13

[GoogleCodeExporter]

Ok .. I need to check the older versions, if this is something that I missed 
during rebuilding the functions.

Original comment by chris.gossmann@googlemail.com on 20 Nov 2010 at 10:24

[GoogleCodeExporter]

The separator tag will never show up on a single post. I checked all the 
versions back to v0.6. If you want to change this behavior, you can create your 
own function called childtheme_override_postfooter_postcategory to override the 
original function.

Original comment by chris.gossmann@googlemail.com on 27 Nov 2010 at 12:27

[GoogleCodeExporter]

Original comment by chris.gossmann@googlemail.com on 27 Nov 2010 at 12:33

• Changed state: WontFix

[GoogleCodeExporter]

Ok, I see your point.  I used the childtheme override to achieve the desired 
style.  That's a very handy feature.  Sorry for the bother.

Original comment by moo...@gmail.com on 29 Nov 2010 at 11:57