- Help Center Home
- Getting started
- Introducing FacetWP
- Installation and updates
- FAQ
- How it works
- What are facets?
- Facet types
- Built-in facet types
- Checkboxes
- Dropdown
- Radio
- fSelect
- Hierarchy
- Slider
- Search
- Autocomplete
- Date Range
- Number Range
- Star Rating
- Proximity
- Proximity private
- Map – private
- Pager + load more
- Sort
- Reset
- User Selections
- Add-on facet types
- Map
- Hierarchy Select
- Range List
- Time Since
- A-Z Listing
- Color
- Legacy facet types
- Proximity (legacy)
- Map (legacy add-on)
- Custom facet types
- Custom facet types
- Indexing
- Listing templates
- Extras & integrations
- Add-on features and extras
- Using FacetWP with …
- Built-in integrations
- Advanced Custom Fields
- WooCommerce
- SearchWP
- WP-CLI
- Add-on integrations
- Blocks
- Bricks
- Elementor
- Beaver Builder
- WP Recipe Maker and Tasty Recipes
- Relevanssi
- WPML and Polylang
- Meta Box
- Flatsome (theme)
- External integrations
- Breakdance
- Document Library Pro
- Listify (theme)
- Listable (theme)
- WPGraphQL
- Tips & tricks
- WordPress multi-site
- WP All Import
- WebToffee Import Export
- WP Job Manager
- Easy Digital Downloads
- EDD Reviews
- Intuitive Custom Post Order
- Custom Taxonomy Order
- Post Types Order
- Genesis framework
- WP External Links
- ElasticPress
- Yoast SEO
- All in One SEO (Pro)
- The Events Calendar Pro
- Google Analytics 4
- Image Optimization by Optimole
- Meow Lightbox
- Cookiebot
- Members
- MemberPress
- Caching, hosting & security
- Object caching
- WP Rocket
- Cloudflare
- WP Engine
- Pressable
- New Relic
- WordPress REST API Authentication
- All-In-One Security (AIOS)
- Fast Velocity Minify
- Incompatibilities
- Incompatible plugins and themes
- Troubleshooting
- Troubleshooting guide
- Using the right query
- Common issues
- Common indexing issues
- Get support
- Developers
- Hooks reference
- Indexing hooks
- Querying hooks
- Output hooks
- facetwp_facet_display_value
- facetwp_facet_html
- facetwp_facet_render_args
- facetwp_facet_pager_link
- facetwp_facet_sort_options
- facetwp_template_html
- facetwp_shortcode_html
- facetwp_render_params
- facetwp_render_output
- facetwp_builder_item_value
- facetwp_builder_dynamic_tags
- facetwp_builder_dynamic_tag_value
- Advanced hooks
- Deprecated hooks
- JavaScript reference
- Shortcodes reference
- FacetWP REST API
- How FacetWP works
- The FacetWP URL
- FacetWP speed and limits
- Tutorials
- Code snippets
- Feedback
- What’s new
- News & announcements
- Changelog
Members
When using the Members plugin (by MemberPress), you may run into disappearing posts or no results at all after using facets.
This issue is caused by the Members plugin filtering out protected posts from WP_Query
, if accessed through the WP REST API. FacetWP uses the WP REST API to retrieve posts with AJAX, when filtering.
To fix the issue for logged-in users only, make sure to pass user authentication data through REST API requests. With this fix applied, you can keep the below-mentioned settings enabled.
To fix this issue for all users (logged-in and logged-out), go to Members > Settings
and make sure the “Hide Protected Posts from WP REST API” setting is disabled. Or disable the “Enable Permissions” setting, which also disables the “Hide Protected Posts from WP REST API” setting:

Instead of disabling the above settings, you can also unhook their function programmatically, only when the WP REST API is used by FacetWP for filtering:
How to use custom PHP code?
PHP code can be added to your (child) theme's functions.php file. Alternatively, you can use the Custom Hooks add-on, or a code snippets plugin. More info
add_action( 'wp_loaded', function() { if ( function_exists( 'FWP' ) && true === FWP()->request->is_refresh ) { remove_filter('posts_results', 'members_filter_protected_posts_for_rest', 10); } });
There is another setting that can be involved, under “Private Site”: “Require authentication for access to the REST API”, which blocks the WP REST API entirely to logged-out users (independent of whether posts are protected or not). This block will cause a 401
error in the browser console on refresh (when filtering) for logged-out users only, leading to non-functioning facets. To fix this, disable the Require authentication for access to the REST API” setting:

Instead of disabling the above setting, you can also unhook its function programmatically, only when the WP REST API is used by FacetWP for filtering:
How to use custom PHP code?
PHP code can be added to your (child) theme's functions.php file. Alternatively, you can use the Custom Hooks add-on, or a code snippets plugin. More info
add_action( 'wp_loaded', function() { if ( function_exists( 'FWP' ) && true === FWP()->request->is_refresh ) { remove_filter('rest_authentication_errors', 'members_private_rest_api', 95); } });
Note that if you are using Members together with the MemberPress plugin, you need to make sure to also apply the fixes for similar issues caused by MemberPress.
See also
- How to pass authentication data through REST API requests
- Why do I have missing posts or no results at all after using facets?
- Using FacetWP with the MemberPress plugin
Last updated: April 3, 2025