Skip Navigation

[Resolved] Taxonomy term filter post counts are all showing 0

This support ticket is created 4 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 9 replies, has 2 voices.

Last updated by Ido Angel 3 years, 2 months ago.

Assigned support staff: Christian Cox.


hmm ok - it works, but now it down;'t show the post count.
i have this code which used to work before the fix:

[wpv-control-post-taxonomy taxonomy="post-typer" type="radio" format="%%NAME%% <span class='orange'>(%%COUNT%%)</span>" orderby="none" url_param="wpv-post-typer"]

i tried rebuilding the index but to no avail...



I'm asking my 2nd tier support team to take a closer look at this one. I noticed that if I combine the View search and results into one single shortcode, the term post counts are different. I'll let you know what I find out.


Just a quick update to let you know my 2nd tier team has figured out how to replicate the issue in a clean site, so the problem is reproducible under specific circumstances. We will continue to investigate and keep you updated here.


thx C.
appreciate it 🙂


hey, any news on this one? cheers.


Hi, nothing new to report yet. At this time the best solution is to combine the search filters and results in a single shortcode. I'll let you know when our developers have additional information.


Can't do, as the search is in the header.. will wait. Thx!


sorry for nagging - any chance this is getting solved soon?


Sorry, no progress to report on this yet. I can see it's been escalated to our compatibility queue, but I don't have any information about when it will be resolved.


My issue is resolved now. Thank you!