Skip Navigation

[Resolved] Display filtered view based on shortcode attribute

This support ticket is created 4 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9:00 – 13:00
14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 - - 14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)

This topic contains 2 replies, has 2 voices.

Last updated by cassianS 4 years ago.

Assisted by: Jamal.

Author
Posts
#1570111

Tell us what you are trying to do?
- I have a custom field (radio button), And I want to display a view filtered by this custom field as a shortcode attribute.
When I insert a custom field as a shortcode attribute I start to receive 0 items.
here is an example of a view shortcode I use {!{wpv-view name='viewname' shortcodeattribute='Custom Field Value'}!}

Is there any documentation that you are following?
- https://toolset.com/documentation/user-guides/views/filtering-views-by-custom-fields/

What is the link to your site?
- hidden link

#1570651

Jamal
Supporter

Languages: English (English ) French (Français )

Timezone: Africa/Casablanca (GMT+01:00)

Hello and thank you for contacting the Toolset support.

Please check this article on how to pass arguments to views https://toolset.com/documentation/user-guides/views/passing-arguments-to-views/

I would like to know have you added the relevant custom field Query Filter to your view at the Query Filter section? It would be great if you can send me a full edit screenshot of your view.

To better help you with this, I'll need to know which values are saved for each radio button option. Can you take a screenshot of the field definition in the fields group?

#1572395

My issue is resolved now. Thank you!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.