[Resolved] custom fields names not displayed with view’s filter select dropdown

[Author]

Posts

[bouchairY]

Hello
I have a view wich list some offers and each offer has some files (pdf, doc ...) attached to it (via ACF Pro)

I want to make a custom search by words in files title and display correspondant offers

Is it possible to do it ?

Thank you for your help

[Minesh]

Hello. Thank you for contacting the Toolset support.

Well - we offer relevanssi integration with view's but it will only support text field, multiline and WYSWYG fields.

More info:
=> https://toolset.com/documentation/user-guides/searching-texts-custom-fields-views-relevanssi/#which-custom-fields-can-i-add-to-relevanssis-index-with-toolset

Could you please check if you able to make it work using above integration.

[bouchairY]

Hello
My metafields are created using ACF Pro
I have Relevanssi premium plugin but don't see
How I can use it to search my title files

Thank you

[Minesh]

ahh - then it would be more complicated then I think. I would love to help you further but I need to check first if its possible or not.

- Have you added the search to your view?
- Could you please share problem URL and access details with one search keyword and what is your expected output.

*** 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 would additionally need your permission to de- and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important. If you agree to this, please use the form fields I have enabled below to provide temporary access details (wp-admin and FTP).

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

[Minesh]

I checked on your install and I see that you are using repeating field from ACF pro and there is no native way to share any solution with you.

This needs pure custom programming which is beyond the scope of our support policy, If you need custom programming for your project, please feel free to contact our certified partner.
=> https://toolset.com/contractors/

[bouchairY]

Hello
I'm creating some metafields related to my custom post type "Offer" : type_de_doc, objet, book, stay
I have found a new solution to my problem but for the moment The "Loop Output Editor" don't display my newly created metafields : type_de_doc, objet, book, stay

I don't understand why !

Thank you for your help

[Minesh]

Well - the difference here is that how ACF and Types store data to database. Types stores all custom field data to postmeta table using standard WordPress API like metakey and metavalue.

As I also confirm that the fields you are using are repeating fields so there is no native way to access the data. Do you see the values are available when you edit your post for the newly created metafields : type_de_doc, objet, book, stay?

[bouchairY]

Hello

Please see here :
hidden link
I have 23 metafields
They are displayed in Views except the last created ones : type_de_doc_new, objet_new, book_new, stay_new
wich are a simple text meatfield NOT repeater

I think it is a bug on Views plugin, I have some repeaters metafield which are dsiplayed in Views why simple text metafields are not displayed ?

Thank you

[Minesh]

If its not repeater field let me check this again as on the post edit link you shared with me before was showing index for field.

Could you please share problem URL where you used to display the view and for which entry it's not displaying the content?

[bouchairY]

Hello

The problem is in the view : SEARCH NEW
hidden link

If you try to add a new filter in the Filter Editor, you will not found the metafields mentionned before to filter by them

Thank you

[Minesh]

Yes - I can see the stay_new, book_new, object_new fields are not available at view's query filter section - I confirm.

I'm bit confuse here - I see you did not installed Types plugin - so does it used to work before without Types plugin and I see the other fields created using ACF under view's query filter section excluding the new fields stay_new, book_new, object_new.

If it used to work before - it should work and I need to investigate further why its not working.

Additionally:
- I see you are using outdated version of "WPBakery Page Builder" - could you please update that.
- Here are few links how you can use "WPBakery Page Builder" with Toolset
=> https://toolset.com/documentation/user-guides/using-toolset-with-wpbakery-page-builder/list-posts-with-custom-searches-and-maps/
=> https://toolset.com/documentation/user-guides/using-toolset-with-wpbakery-page-builder/create-templates-for-custom-post-types/

[bouchairY]

Hello

Please see this thread
https://toolset.com/forums/topic/non-types-metafields-not-listed-in-the-filter-editor/

I have had this problem before with search and was fixed without doing anything !!!

Thank you

[Christian Cox]

Hi, Minesh asked me to look at this ticket since he is in a different timezone.

They are displayed in Views except the last created ones : type_de_doc_new, objet_new, book_new, stay_new
In the screenshot you provided, it looks like these are ACF fields, not managed by Types. If these fields are not managed by Types, they may not be used as Views filters. Fields must be managed by Types to be used as Views filters effectively and consistently. In the other ticket, the problem was not resolved by any changes from the Toolset team, so I'm not sure how to replicate that solution.

[bouchairY]

Hello
CAN you explain Why all existing metafields are available on filtre except the last Created ?
Normally, they are all available or all not available except if there us a bug on views plugin !!
Thank you for more investigations

[Christian Cox]

A bug implies something that is supposed to work, does not work. ACF fields are not supposed to work as Views filters. I cannot explain why sometimes they work and sometimes they do not work.