you have a Fields control section, to bring arbitrary custom fields under Types control but please acknowledge that radios fields, select fields, checkboxes fields, date fields, etc, have specific formats in different plugins.
So anything that is not a string or a number will be probably be broken after bringing those fields under post field Control.
If you can not find the Custom Field's at: Toolset => Post fields => Post field Control, it's because those fields are not stored as default WordPress Custom fields (post_meta), and Types can't find them most probably because those are stored in custom table in the Database.
I am seeking for clarity of how to use Toolset plugins to access the woocommerce native fields for custom search, ie to recreat the price slider of the price which I will lose after I use my own Toolset archive pages.
I was hopping to build a search page to clone the woocommerce native product archive page with those price slider and taxonomy checkboxes on the right sidebar.
Please advice what is the best approach to clone the native functionalities.
if there are fields from WooCommerce or other plugins Toolset plugins for example Types does not support them automatically unless we add them for third party support.
is it true that these are native fields
==> yes it looks like they belongs to third party like WC but please acknowledge that radios fields, select fields, checkboxes fields, date fields, etc, have specific formats in different plugins so anything that is not a string or a number will be probably be broken after bringing those fields under post field Control.
is it true that remaining native wc fields not accessible by toolset
=> no , but we can add them to types support enabled fields
-> is it the reason why woocommerce views create its own fields
==> yes, because we want user to automatically use our fields for filtering purposes without having them add those fields manually
To sync the values from WC to Woocommerce views as you shown with the following image:
=> hidden link
if there are fields from WooCommerce or other plugins Toolset plugins for example Types does not support them automatically unless we add them for third party support.
is it true that these are native fields
==> yes it looks like they belongs to third party like WC but please acknowledge that radios fields, select fields, checkboxes fields, date fields, etc, have specific formats in different plugins so anything that is not a string or a number will be probably be broken after bringing those fields under post field Control.
(new Question regarding your above answer)
======>> is it mean the reliably support third party native fields will be string and numeric ??
is it true that remaining native wc fields not accessible by toolset
=> no , but we can add them to types support enabled fields
(new Question regarding your above answer)
======>> please show me how to add them
-> is it the reason why woocommerce views create its own fields
==> yes, because we want user to automatically use our fields for filtering purposes without having them add those fields manually
(new Question regarding your above answer)
======>> please give an example for adding a different view to access other fields of wc product, step by step.
My purpose is to learn how to access any 'exposed fields' of a third party custom post type from a plugin, ie other fields of woocommerce products ( other than price, on-sale or in-stock)
Step 2: Now insert fields into a View: please go to: Toolset >> Views >> Edit/Add a View >> In Content Selection select “Products”
Step 3: Now you can add fields in Views and in Query Filter
- For View: In Loop Output Editor >> Fields and Views button >> Post fields >> Load non-Types custom fields (see attached screenshot: Load fields.png)
- For Query filter: In Query Filter >> Add a Filter button (see attached screenshot: query filter.png)
2. Further as I can see you would like to recreate WC Price Slider for filtering. WooCommerce by default offers a “Price Filter Widget” which you can use in your site (see attached screenshot: WC Price filter). It's a very complex field type and Toolset does not offer this field type so recreating this is not possible without doing custom coding.
