Hi Minesh,
Finally found (and removed) the problem js code in "Edit View - header for Javascript" section
Now "Florapal home page" is not throwing any js errors.
Thanks
Minesh
Supporter
Les langues:
Anglais (English )
Fuseau horaire:
Asia/Kolkata (GMT+05:30)
Can you please check with this test page I've created: lien caché
As you can see with the above test page, I've added one taxonomy select filter using the following view:
=> lien caché
And added the following JS code to view's JS box:
jQuery(document).ready(function($){
$("select[name='wpv-botanical-name']").on("change",function(){
window.location.href = window.location.origin+"/?plant="+this.value;
});
});
Now, if you try to change the select dropdown option it will redirect you to that specific plant page.
You can add your other taxonomy filters to the above view and adjust the above JS code so that the same JS code should apply to all of your desired select box you add.
Hi Minesh,
Thanks very much for this - works perfectly.
But my JS coding skills are very poor, so please could you just add the English name taxonomy select box, so I can see how to add multiple filters.
Thanks
Minesh
Supporter
Les langues:
Anglais (English )
Fuseau horaire:
Asia/Kolkata (GMT+05:30)
The thing is that - we can not add dropdown for English Names because basically we are using the slug of the taxonomy.
For example:
If we select the term "Acacia strap flower" from the select dropdwon:
=> lien caché
It will redirect us to the page: lien caché
But when I checked for Acacia strap flower, it uses the different slug "plicosepalus-acaciae-zucc-wiens-polhill":
=> lien caché
There is no way to identify that if I select "Acacia strap flower", it should be redirected on post with slug ""plicosepalus-acaciae-zucc-wiens-polhill", as there is no mapping.
So, it seems you need to use the manually code you are using because there is no way to map the slugs of taxonomy term to post slug.
Thanks very much Menesh for you help