fesupportteam
Forum Replies Created
-
Hi @jerclarke
There was a conversation regarding this. However, the only reason why this wasn’t applied is because, as long as no filters are selected on the page, nothing is basically working other than displaying the filters themselves. Also, in some cases, this output could display the wrong number of products if it were displayed before applying any filters. This was specifically added only to display the amount of found products after applying the filtering.
It could be changed in future updates (we already have it on the list), but for now this counter only relates to the filtering itself, not as a global product counter before filtering.
Generally, you can use templates overriding: https://filtereverything.pro/resources/templates-overriding/ for the posts-found.php file and apply your own custom code to display the required counters in the way that would fit your case.
Best Regards,
VictorHi @thewebmonk
Thank you for the update on the issue and for sharing the solution.
Could you please let us know if this solution resolved the issue after its implementation?
Best Regards,
Victor@mingjamoves Based on the provided image, if you want to use multiselect terms, you need to choose OR logic and not AND logic. OR checks if any of the chosen terms are applied to the products, while AND looks only for products that have all selected terms applied.
Best Regards,
VictorHi @mingjamoves
Can you please clarify what exactly is now showing on the shop page? Perhaps there was a link to the image that was not included in the message itself?
Additionally, you can check the support page once again on our official site. There is also contact information in the footer for additional information regarding PRO support if you are having any difficulties receiving it or finding the right form where to post it.
Best Regards,
Victor@thewebmonk This is quite a complicated case, as it would usually require some debugging to understand what could have caused it. If you could contact us through PRO support, we could check this further and ask for any additional required information.
For that, you can check our official support page here: https://filtereverything.pro/support/
Best Regards,
Victor@mingjamoves The PRO version uses permalinks instead of query parameters, so instead of ?color=red you get the /color-red/ format.
Best Regards,
Victor@mingjamoves The query separators are configured on the server side or at the hosting level. As you can see in this link example: https://myameritex.com/all-products/?fe_cat=sharp;xerox&fe_brand=color, the parameters in the URL are separated by the symbols “;” and “&”. On the server level, these can be configured to be treated the same way as “&”, so this should be adjusted accordingly.
You can now return the site to its initial state by turning the other plugins back on.
Best Regards,
Victor@mingjamoves Thank you for that. We have managed to check the page without the page builder and how it is working.
Perhaps you have extra configurations for the query separators on the server, where in some cases the server can be configured to treat both “&” and “;” symbols the same way. Since “;” is used for OR logic, this can cause similar behavior. In such cases, the query separator settings should be adjusted on the server side.
Best Regards,
Victor@mingjamoves You can leave a message regardless of whether you purchased the PRO plugin or not.
Yes, can you please turn everything off, then go to the filter set and click the Update button after turning everything off so the plugin can work with the default main query, and then let us know so we can check the page.
Best Regards,
VictorHi @thewebmonk
Did you follow this documentation page during the translation of the filter sets? https://filtereverything.pro/resources/with-wpml-polylang/
It is important that every language contains a separate filter set in the required language.
Best Regards,
Victor@mingjamoves You can try contacting us via PRO support by following the instructions on this support documentation page: https://filtereverything.pro/support/ so we can get more information about this matter.
Currently the whole page is still using the Elementor: https://prnt.sc/jIfVVQM78xk-
Best Regards,
Victor@mingjamoves In that case, it could be a conflict with custom code or custom templates from page builders that apply extra settings on top of the main query. The free version of the plugin does not work with custom queries that page builders can apply.
Please try the following on the staging site:
Fully deactivate the page builders, custom code, and all unnecessary plugins, leaving only the required ones active, such as Filter Everything, WooCommerce, and the default 2019 theme, since that is the one you are currently using.
Then apply the filters to the shop page and check whether they are working correctly. (We just tested it on our side with that theme, and it worked correctly.)
If the filters work properly, you can then reactivate the remaining plugins, page builders, and custom code one by one to identify which one is causing this behavior.
Please let us know if you manage to make it work on the clean staging environment without extra plugins and using the default 2019 theme.
Best Regards,
VictorHi @mingjamoves
Try going to Filters > Settings > SEO > VAR Names and changing the current names to something more unique, such as fe_cat, fe_brand, and so on, using underscores, just for testing purposes.
After making all of the modifications, click the Save button at the bottom of the page. Then go back to your filter set, refresh it, and click the Update button.
After that, open the page with the filters, clear your browser cookies and cache, and test the filtering again to see if it works correctly.
Best Regards,
VictorHi @gjfo
If you are referring to filtering another post type that will contain FAQ posts and any other information, then yes, you can use this plugin: https://ww.wp.xz.cn/plugins/custom-post-type-ui/ to create the required custom post types. With the same plugin, you can also add custom taxonomies to your newly created post type.
Best Regards,
VictorHi @jpnl
Thank you for sharing the detailed review. We will make sure to prevent such modifications in the future in order not to cause any issues.
Best Regards,
Victor