[wp-hackers] current_page_ancestor class lost on Tertiary pages?

Dan Smart dan at dansmart.co.uk
Tue Sep 14 21:11:22 UTC 2010

The issue you have is that the menu doesn't look at the page hierarchy, only the menu hierarchy. So you need to add X1 to X22 to the menu, then the correct classes will appear.


Dan Smart - Web Developer

On 14 Sep 2010, at 20:31, Louis McCoy <louie at louiemccoy.com> wrote:

>> How deep are these levels?  Can you be more specific about the overall
>> menu structure or link to an actual example?
> It's just the third level - I should have been more clear; it's not the menu
> that is three levels deep, it's the page structure. So, this is the page
> structure:
> I. Foo
>  A. Bar
>    1. X1
>    2. X2
> ...
>    22. X22
>  B. Saloon
>  C. Tavern
> II. Foo Fighers
> III. More Foo
> But this is the menu structure, since the menu by design doesn't go deeper
> than two levels:
> I. Foo
>  A. Bar
>  B. Saloon
>  C. Tavern
> II. Foo Fighters
> II. More Foo
> BUT, once I get to X1 / X22 etc. Foo loses the current_page_ancestor class.
> Is this just because they're not a part of the menu structure? Shouldn't
> Foo, being an ancestor of X1, still keep the current_page_ancestor class,
> even if X1 isn't in the menu structure?
> Hope I was clearer this time... :-)
> -L
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list