Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I create a exposed filter of field field_nick_name
.
and I visit this link http://drupal/daxuebao/api/views/user_search_by_nick?filters[field_nick_name]=a
.
But can not work.
Comments
Comment #1
bezprym CreditAttribution: bezprym commentedYou should check your services, do you have access to that view in your api services.
Comment #2
ibraaheem CreditAttribution: ibraaheem commentedIt actually works for me. My issue is with exposed filter text containing space. Using + or %20 is not working
Comment #3
ibraaheem CreditAttribution: ibraaheem commentedEventually got it to work using # between the two words.
Comment #4
DrupalWoody CreditAttribution: DrupalWoody commentedComment #5
DrupalWoody CreditAttribution: DrupalWoody commentedFiltering is not working period. It does not work for node IDs or any other feature of my content.
Comment #6
dbassendine CreditAttribution: dbassendine commentedMake sure you don't have Captcha module enabled with the "Default challenge on non-listed forms" option (in admin/config/people/captcha) set to on. This configuration broke the entire services views endpoint when exposed filters were added to the view, regardless of whether they were called in the URL or not.
Hopefully this will save someone some time!
Comment #7
sano CreditAttribution: sano as a volunteer commentedExposed filters work ok for me. I encountered some problems when filtering by taxonomy ID, for which I had to create a relationship to get the actual term ID. The key in the service url must be the field name.