Taxonomy Archives 404

  • Resolved fesarlis

    (@fesarlis)


    2 months, 1 week ago

    Hello.

    Let me describe a rather hidden issue which has been solved in a dirty way. Please also have a look at my previous post, which is definitely connected to this one.

    A store must be unambiguous. I have given too much time and effort on this. But:

    If we have a taxonomy (eg product category) filter, it is now clear that filtering by category does not produce the same result as viewing the taxonomy archive (see previous post). Therefore, I have converted all my store links that used to go to taxonomy archives to now go to the URL produced by Filter Everything.

    This has an interesting side effect: The link produced by Filter Everything (eg /shop/category-keyboards) will produce a 404 if this filter is not created. I can understand this. But inside the filter set settings, the user MUST choose something on ‘Where to filter’. This definitely shouldn’t be required.

    Eg, in my case, I have a Brands menu, which lists all Brands and each link goes to /shop/brand-dell, instead of /shop/brand/dell (the Brands taxonomy archive) because in such a case ambiguity would be introduced (no chips, different terms etc). Yet, I really want the brands to be accessible only from a menu and not on a sidebar or widget. So this filter set really does not need to have a location set since it is used in a different way.

    The obvious dirty workaround is to select a location which is not going to be used ever, but this cannot be acceptable since their number is finite.

    Sorry if I don’t make much sense, please let me know, and please consider making this setting optional.

    Thanks

Viewing 1 replies (of 1 total)
  • Plugin Support fesupportteam

    (@fesupportteam)

    Hi @fesarlis

    We are going to provide a small description of how the filter works what it is filtering and why “Where to filter” which is only available in the PRO version is important.

    The Free version is displayed by default on all archive pages connected to the post type that you need to filter. And will work only with the main query on the page. Meaning if there are two or more queries on a page it won’t filter anything on this page. (which most page builders do or themes they use custom queries).

    For this, in the PRO version, there is an option available “Where to filter”. For example, you have 3 singular pages, and they all have different unique queries that display your posts. In order to filter your posts you need to choose in the “Where to filter” dropdown the needed page and then in the “And what to filter” choose the needed query to work with. (the exact query that displays posts on your page)

    Now, if we remove this option, you have 100 pages on your site, those pages can contain multiple queries, on which page and which query should be chosen in order to filter your posts and not some type of menu or slider or anything else?

    For your case, you can simply remove filters created by categories and tags and any taxonomy, create simple archive page crawlers, and make filters by custom fields, product attributes, and so on.

    The filter purpose is to filter posts on the exact page as you need, if this is a page from Taxonomy Cars but there are posts from another taxonomy Shoes, it will filter them all on the cars category page, instead of redirecting to the shoes category and cars category back and forth.

    The taxonomy pages and filtering particles are not connected and should not be connected. If there is a shop page, that displays all of the products, you can filter products on that page by as many categories as you need. You can choose to display posts from cars and from shoes at the same time, there are no archive pages that are connected like that and display them both, you cannot create the same link for filters as for category pages, as it will cause errors.

    Best Regards – Victor

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.