Toolset Access and FacetWP are not compatible

Symptoms

The FacetWP plugin doesn’t work correctly when the Access plugin is also active. For example, if you add a custom search and try to filter by taxonomy, the FacetWP filter is ignored and a full list of posts is rendered. The issue is actually caused by the FacetWP plugin, which is running the init filter before everything else.

If you use FacetWP while Access is active basically all FacetWP’s AJAX-based features like search results and pagination will fail.

Workaround

FacetWP modifies the Main Query with additional parameters and runs another WP_Query instance to show search results.

Here is a short explanation of what happens:

• When Toolset Access tries to check/set permissions for the Custom Post Types, it runs the toolset_access_get_current_page_id function that, in turn, runs the url_to_postid WordPress core function.
• That url_to_postid function runs another WP_Query that replaces the result from the FacetWP’s query and completely breaks the results from FacetWP.

This happens because of the late priority of Access and the early priority of FacetWP. At this point, this issue cannot be resolved.