Make WordPress Core

Opened 20 years ago

Closed 19 years ago

#3049 closed defect (bug) (fixed)

wrong class attribution for wp_list_pages when author template is called...

Reported by: tripleshift Owned by:
Priority: normal Milestone: 2.1
Component: Template Version: 2.0.4
Severity: normal Keywords: wp_list_pages, current_list_item, author.php
Cc: Focuses:

Description

i recently came across this issue while studing the wordpress template system and functions.

if i got it right, "wp_list_pages" function is supposed to give a "current_page_item" class to the list item whose page is actually called.

i noticed that when the author.php template is called through "the_author_posts_link" function, and the ID of the user/author called is the same of one of the pages, the page list item generated by "wp_list_pages" gets the "current_page_item" class as well.

example:
user "john doe" with "id=3" has 3 posts and through a link generated by "the_author_posts_link" (put inside the loop) gets his post listed in a page generated through the auhtor.php template.

if the condition exists that one of the existent pages (listed by "wp_list_pages") has id="3" (the same as the user/author), then a "current_page_item" class is given to the list item containing the link to the page, even if the page IS NOT "current".

i truly hope what i wrote was clear, i truly hope i didn't file an already existent report.

bye
tripleshift

...

Change History (11)

#1 @ryan
19 years ago

  • Milestone2.1.1

#2 @ryan
19 years ago

Does the same with categories.

#3 @ryan
19 years ago

  • Resolutionfixed
  • Status newclosed

(In [4863]) Check page ID only if is_page. fixes #3049

#4 @ryan
19 years ago

(In [4864]) Check page ID only if is_page. fixes #3049

#5 @ryan
19 years ago

  • Milestone 2.1.12.0.9
  • Resolution fixed
  • Status closedreopened

Fixed for 2.1.1 and 2.2. Leaving open for 2.0.9 consideration.

#6 @Nazgul
19 years ago

  • Milestone 2.0.92.0.10

2.0.9 is out, so bumping the milestone to 2.0.10.

#7 @foolswisdom
19 years ago

  • Milestone 2.0.102.0.11

#8 @foolswisdom
19 years ago

  • Milestone 2.0.112.0.eventually

#9 @Nazgul
19 years ago

  • Milestone 2.0.eventually
  • Resolutionwontfix
  • Status reopenedclosed

Closing as wontfix for the 2.0 branch.

MarkJaquith has stated that only security fixes can go into the 2.0 branch.

#10 @foolswisdom
19 years ago

  • Resolution wontfix
  • Status closedreopened

#11 @foolswisdom
19 years ago

  • Milestone2.1
  • Resolutionfixed
  • Status reopenedclosed
Note: See TracTickets for help on using tickets.