[Resolved] Query filter / Sliders based on SKUs from a multiple values field

[Author]

Posts

[maximilianD]

I have added a custom field called "accessoires" to my products. The custom field contains SKUs to other products on the page, that are accessoires of the given product.

How can I set the query filter of the view to work with multiple values e.g SKU: 11-123, 11-124...

My goal is to show a slider with products, that are accessoires of the main product.

[Minesh]

Hello. Thank you for contacting the Toolset support.

Well - please check the following doc that will help you to understand how you can filter your view results by custom field:
=> https://toolset.com/documentation/user-guides/filtering-views-by-custom-fields/

When you try to add a custom field filter, you can chose how you want to display your custom field filter on frontend:
- checkboxes
- select
- multi-select
- radio button

In addition to that - there is no such native feature available to implement the slider filter with Toolset and there is no simple way to implement it.It will require lots of custom code, including knowledge of advanced jQuery and HTML and CSS customizations.

If you search the forum, you will find the number of tickets like you shared one already but there is no solution available. To implement such feature really needs significant customization with HTML, CSS, jQeury, PHP and Tooslet hooks and to support such custom edits is beyond the scope of our support policy: https://toolset.com/toolset-support-policy/

As a supporter, we need to work within the defined support boundaries, as a result, I do not have any solution to offer you here. I've two things to offer here, either contact our certified partners for such custom code.
=> https://toolset.com/contractors/
OR
Submit a new feature request:
=> https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/

[maximilianD]

Sorry, that is not what I mean.
I'm not talking about filters on the front end.

I meant query filter options on the page where I create a custom view.
I try to create a slider (view) which I can insert on my product page.

The slider should show accessoires products that fit to the product where this view is shown.

On the main product itself, I have created a custom field where I save the SKU of the accessoirie products.

[Minesh]

I see SKU field is a repeating field.

AS I understand, you want to display the posts as slider using slider view where the SKU is matched as per the query filter adeed - correct?

Can you please share problem URL and access details.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

[Minesh]

Ok - as I understand, you wanted to display the products whose SKU belongs to the values of the field "original-types-field-name"? so if there are 5 values show those 5 products belongs to those SKUs and if there are 10 values show those 10 products belong to that SKU?

[maximilianD]

Thats correct. (Please remove the brand name from your last post, as i don't want it to be found by google.)

[Minesh]

Ok - I've removed that word from my previous post.

Please check - I've changed the view slug as we should not have duplicate slugs that should conflict with psot type, custom field slugs etc..etc as well as I changed the query filter that should query the field _sku:
hidden link

I've added the view as given under:

{!{wpv-view name='zubehoer-view' sku='{!{types field='zubehoer' separator=', '}!}{!{/types}!}'}!}

Can you please check now and confirm you get expected results or still am I missing here anything:
hidden link

[maximilianD]

Thank you very much. 🙂

[maximilianD]

P.S. Please remove the domain from your link. Thank you !

[Minesh]

Yes - removed. thanks 🙂

[maximilianD]

My issue is resolved now. Thank you!