Multiple filters on one page all updating
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from Adam on June 10, 2020, 17:20For reasons that make sense to me (!), I have split filters on a single home page with three shortcodes. One for step-search [woof_step], one for specific text search and one for another taxonomy (both [woof]).
When I use the step search, the other two filters update to reflect the step filter, meaning all three filters show the step search.
Before: https://tinyurl.com/ybjf4p4z
After: https://tinyurl.com/ycuywpaz
How can I stop the other two filters on the page updating when the the step filter is used?
Thanks
For reasons that make sense to me (!), I have split filters on a single home page with three shortcodes. One for step-search [woof_step], one for specific text search and one for another taxonomy (both [woof]).
When I use the step search, the other two filters update to reflect the step filter, meaning all three filters show the step search.
Before: https://tinyurl.com/ybjf4p4z
After: https://tinyurl.com/ycuywpaz
How can I stop the other two filters on the page updating when the the step filter is used?
Thanks
Quote from Pablo Borysenco on June 11, 2020, 12:29Hello
only one filter(widget,shortcode) can work on one page
Hello
only one filter(widget,shortcode) can work on one page
Quote from Adam on June 11, 2020, 16:21That's quite a limitation.
So we can't combine a step filter with standard filters either?
That's quite a limitation.
So we can't combine a step filter with standard filters either?
Quote from Adam on June 11, 2020, 17:25I have an issue. As you can see, I need visitors to be able to select make/model/year or part number from the home page. The step filter was one of the appeals of the theme selected. I can't have part number in [woof_step] and I can have a [woof_step] with a [woof] on the same page. So I have to use one [woof] only. However, I don't want it to start filtering until make, model and year is selected, otherwise a soon as make is selected it jumps off to to the shop page displaying all parts related to Make.
So that would mean I need to have autosubmit=0, but then it means once make is selected, nothing happens. Can't then select model/year.
Basically, I need the feature of woof_step while still having other filter options. But it seems the way it's designed/implemented, you can only use either a step filter or standard on one page. Correct?
If there's any workaround I can employ to force the make/model/year filter to update without actually redirecting to the shop page as soon as make is selected, but wait until the filter button is pressed?
I have an issue. As you can see, I need visitors to be able to select make/model/year or part number from the home page. The step filter was one of the appeals of the theme selected. I can't have part number in [woof_step] and I can have a [woof_step] with a [woof] on the same page. So I have to use one [woof] only. However, I don't want it to start filtering until make, model and year is selected, otherwise a soon as make is selected it jumps off to to the shop page displaying all parts related to Make.
So that would mean I need to have autosubmit=0, but then it means once make is selected, nothing happens. Can't then select model/year.
Basically, I need the feature of woof_step while still having other filter options. But it seems the way it's designed/implemented, you can only use either a step filter or standard on one page. Correct?
If there's any workaround I can employ to force the make/model/year filter to update without actually redirecting to the shop page as soon as make is selected, but wait until the filter button is pressed?
Quote from Pablo Borysenco on June 12, 2020, 14:00Hello
Please drop me exact link to this issue
Hello
Please drop me exact link to this issue
Quote from Adam on June 12, 2020, 15:54I've had to drop the [woof] filter and use only the [woof_step] filter without the part number (meta text) search. So can't show you now. But have included site link. Customers will have to get into the product listing before they can do a part number search.
You can replicate easy enough if my explanation is not clear. See the images above. Make/model/year is a single taxonomy (make_model), with make parent of model and model parent of year. This is implemented with the "Make+Model+Year" Taxonomy custom label trick to gave three selectors on the same taxonomy.
When done with [woof_step] it works ok, not moving to the product listing until year is selected. But can't have part number search.
When done with [woof], can have part number search but make/model/year immediately redirects to listing page when make is selected. With autosubmit=0, nothing happens after selecting make; model doesn't update so it can be selected.
I've had to drop the [woof] filter and use only the [woof_step] filter without the part number (meta text) search. So can't show you now. But have included site link. Customers will have to get into the product listing before they can do a part number search.
You can replicate easy enough if my explanation is not clear. See the images above. Make/model/year is a single taxonomy (make_model), with make parent of model and model parent of year. This is implemented with the"Make+Model+Year" Taxonomy custom label trick to gave three selectors on the same taxonomy.
When done with [woof_step] it works ok, not moving to the product listing until year is selected. But can't have part number search.
When done with [woof], can have part number search but make/model/year immediately redirects to listing page when make is selected. With autosubmit=0, nothing happens after selecting make; model doesn't update so it can be selected.
Quote from Pablo Borysenco on June 15, 2020, 11:56Hello
Paste your license key here - https://c2n.me/43SC6rb.png -> https://c2n.me/42HBIt7.png
Update plugin to latest version - https://products-filter.com/how-to-make-auto-update-for-wordpress-plugins-and-themes-bought-on-envato/
Hello
Paste your license key here - https://c2n.me/43SC6rb.png -> https://c2n.me/42HBIt7.png
Update plugin to latest version - https://products-filter.com/how-to-make-auto-update-for-wordpress-plugins-and-themes-bought-on-envato/
Quote from Adam on June 18, 2020, 15:58Hmm, seems I forgot to submit my last reply!
Are you saying there's an update that addresses this issue? As mentioned elsewhere, your extension came bundled with the theme. But if there's an update to address this I'll purchase it.
Hmm, seems I forgot to submit my last reply!
Are you saying there's an update that addresses this issue? As mentioned elsewhere, your extension came bundled with the theme. But if there's an update to address this I'll purchase it.
Quote from Adam on June 18, 2020, 17:13Well this isn't going well! Followed the guide on enabling Envato API token but it fails to authenticate (yes, I've done it twice to be sure). If I enable Verify purchases you've made, it fails on that. If I disable that and just enable the recommended permissions, it fails with a 403 (forbidden) error. This is an Envato issue rather than your plugin.
So I thought I'll download and install it. Now it get's really confusing! According to plugin list, version is 2.2.2.1. But click details and it takes us to Wordpress.org where current version is 1.2.4! Opening the latest download I see it's 2.2.4, so you maybe typo'd there?
Further, WC plugin check says it's only tested to 3.5.1. when 4.2 is now ready to install?
Anyhow, now installed 2.2.4 so what can I expect from that wrt this ticket?
Well this isn't going well! Followed the guide on enabling Envato API token but it fails to authenticate (yes, I've done it twice to be sure). If I enable Verify purchases you've made, it fails on that. If I disable that and just enable the recommended permissions, it fails with a 403 (forbidden) error. This is an Envato issue rather than your plugin.
So I thought I'll download and install it. Now it get's really confusing! According to plugin list, version is 2.2.2.1. But click details and it takes us to Wordpress.org where current version is 1.2.4! Opening the latest download I see it's 2.2.4, so you maybe typo'd there?
Further, WC plugin check says it's only tested to 3.5.1. when 4.2 is now ready to install?
Anyhow, now installed 2.2.4 so what can I expect from that wrt this ticket?
Quote from Pablo Borysenco on June 19, 2020, 12:17Hello
Try to use this shortcode:
[woof ajax_redraw=1 autosubmit=1 by_step='make_model']
If no luck - drop me wp-admin+FTP access
Hello
Try to use this shortcode:
[woof ajax_redraw=1 autosubmit=1 by_step='make_model']
If no luck - drop me wp-admin+FTP access