Hi,
Based on my previous support ticket here:
https://toolset.com/forums/topic/pagination-of-wordpress-archives-not-working-for-me/
with your help, I was able to automatic archive taxonomy pages with taxonomy filters.
here are the results:
hidden link
hidden link
when I choose any option from the dropdown lists, the posts filter accordingly.
However, I wanted to create another layout for other custom taxonomies. I duplicated the layout above, and tried to adjust it. however, the filters will not work at all.
the values in the dropdown are correct. however, choosing any value from it doesn't change anything. The ajax works, but posts don't get filtered.
The pagination works. so the view works. but for some reason the filteration doesn't work:
here are some examples:
this is an archive page showing posts from a CPT called "magazines" that has 2 custom taxonomies. "Publications" and "Dates". where the publication is the magazine name, and the dates shows the years of these magazines.
when i filter by either dropdown, nothing happen.
hidden link
this one is for an archive page of one of the publications, so the "publications" dropdown shows the magazine name correctly, but when i choose any year, nothing happen.:
hidden link
can you please help me identifying why the original layout and views work, while the duplicated ones don't?
thanks
Hello,
Thanks for the details, in the archive page
hidden link
It is using Views wordpress archive:
hidden link
I have modified above wordpress archive, in section "Query Filter", change the URL parameter name:
from "wpvpublication" to "wpv-publication"
from "wpvdate" to "wpv-date",
The URL parameter name should be same as your settings in section "Search and Pagination":
[wpv-control-post-taxonomy taxonomy="publication" type="select" default_label="ALL" url_param="wpv-publication"]
...
[wpv-control-post-taxonomy taxonomy="date" type="select" default_label="ALL" url_param="wpv-date"]
Please test again, check if it is fixed, thanks
Hi Luo,
Thanks a lot for the fix.
yes it works. however, the naming was done automatically by the plugin. i did not change any naming. if the plugin generates different naming like this, then can you please report this to the development team?
i lost several hours of work yesterday trying to get this to work, and it is not the first time that things don't work out becasue of the (-) in the naming.
i appreciate if you report this please.
thanks a lot.
How does the naming was done automatically by the plugin?
Can you describe detail steps to duplicate the same problem? thanks