Conflict with ACP + ACF

  • Hello,

    A lot of my sites use both Advanced Custom Fields and Admin Columns Pro. I discovered recently that the ACP column filtering was resulting in no results. After a lot of back and forth with ACP support and investigating myself, we came to the realization that the issue went away when Search Everything was disabled.

    I saw a similar post here regarding bbpress, where debugging showed an oddity in the SQL query. Here’s mine:

    SELECT SQL_CALC_FOUND_ROWS wp_posts.ID
FROM wp_posts 
INNER JOIN wp_postmeta
ON ( wp_posts.ID = wp_postmeta.post_id )
WHERE 1=1 
AND ((())) 
AND ( ( wp_postmeta.meta_key = 'product_internal_id'
AND wp_postmeta.meta_value = '1105' ) )
AND wp_posts.post_type = 'product'
AND (wp_posts.post_status = 'publish'
OR wp_posts.post_status = 'acf-disabled'
OR wp_posts.post_status = 'future'
OR wp_posts.post_status = 'draft'
OR wp_posts.post_status = 'pending'
OR wp_posts.post_status = 'private')
GROUP BY wp_posts.ID
ORDER BY wp_posts.post_date DESC
LIMIT 0, 20 /*

    Thinking that something must have changed recently with Search Everything, as I’ve been using it for quite some time without any problems.

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Sovrn

    (@sovrn)

    Hi @relish1227,

    Thanks for reaching out and we apologize for the inconvenience. When did you first start to notice the errors and plugins conflicting? We would love to get a timeline to determine whether or not an update, or which section of an update, caused this particular issue.

    Best,
    Sovrn Support

    Thread Starter relish1227

    (@relish1227)

    Hi, Sovrn.

    It looks like I contacted Admin Columns Pro support on April 5th. The first time I searched for and found the query that included the “WHERE 1=1 AND ((()))” was on April 7th. There were some separate issues with ACP that got resolved by April 12th. However, I continued to have a different (although seemingly related) issue with ACP after that. Some time passed in which my ticket got lost in the support wilderness, but eventually ACP helped figure out that somehow the Search Everything plugin was causing the issue.

    Here’s their notes:

    “It’s the ‘search everything’ plugin. It always adds the ‘s’ to the query and that causes the the invalid SQL. My first hunch is that this plugin has no reason to add a search query on a filter request. Once that plugin is disabled, all works fine again.

    “If I disable Admin Columns and try to filter on a regular WordPress date, it also stops working properly. Maybe you can check that as well? So I would like to conclude that search everything simply oversteps it’s boundary and should only work on the search form and nothing else.”

    I had previously deactivated all plugins, but this was before the April 12th fix of a different ACP issue. I should have done so again afterwards to come to this conclusion as well.

    Hoping that this helps you identify the issue! Thanks for the response.

    Thread Starter relish1227

    (@relish1227)

    I am working on a new site now and noticing this issue again. Do you have any updates on why this is happening? Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with ACP + ACF’ is closed to new replies.