Eli Antebi

The basic and “stupid” solution is just to make a loop on the posts table at the top of the single page, and run the increment like the archive, and once I got to the same post ID – stop the loop and capture the counter. heavy but works.

The big picture is a bit complicated:

I have Players CTP
Each Player related to one Team taxonmy

The Team archive page shows a list of playes in a given team (taxonomy), which the UI-design required to show its fake-ID, lets say “01/200”, “02/200″…. “200/200”. The 200 refers to the amount of players in this specific team (taxonomy).

I also have client-side filters on that archive page, like “show only male”. That filters the list to let say 150 players, who should keep their fake-ID visible. Not big deal since it’s on the client side and I just show and hide irrelevant players.

Now here’s the problem: On the single page, where I should show this player fake-ID, I should also show next/prev player link which should take into consideration the male/female filter 🙂

I cant guess what is the next mache post and what would be it’s sort-index on that filtered taxonomy…That’s why I must have a DB key for the ordering, one that I query the database based on it… So I find the current one, and simply quesry the following.

Thanks anyway!!