Ok, finally found the reason for this issue. I was using some script that conflicted and modified the search string. It was essentially searching for a blank string each time. The script I was using was to fix some search issue with the media library page here. Anyway, the accepted answer here WILL conflict with this ACF field.
Shoot, can’t replicate that fix :/ The list just gets locked on the first post of the “Posts” post type and won’t drill down any deeper. It doesn’t even hide the posts in the “Posts” post type that don’t match the query. Just like in my original screenshot.
Ones last question, how many total News posts and Event posts do you have? Are there more than 20, or less than 20?
I’ll look at this a little closer later on. There must be some difference in the way I have things setup that’s causing this issue. I appreciate your help on this!
Ok, I can confirm that your fix works when only using a single post type filter. However, it doesn’t fix the issue for me when multiple are selected (or when nothing is selected, which is essentially “All”).
Is this something you could test and confirm on your end?
Oh ok, yeah, I was using a page link instead of a post object. However, it still doesn’t seem to be fixing the issue.
One question about your setup: with your custom field, are you using any of the “Filter by Post Type” types? Or are you just leaving that field blank? That’s the only difference I can think of between are setups.
Hey aaronjheinen, thanks for posting your solution. I gave it a try, but the behavior doesn’t seem to be fixed for me. I might be placing the filter in the wrong location though. I added it to my functions.php file. Should I be adding that code somewhere else?
Hey, just updated to the latest quick fix version and it doesn’t seem to be behaving the same as the fix you posted in the ZIP file above. With the ZIP, it seemed to be fixed, but now I am seeing different behavior with the actual update.
The content for both my tabs are showing on page load, and no tab is shown as selected. No JS console errors or anything.
This is how it looks when it loads:
This is how it should look though, I get it to do this when I explicitly click “Section Options”:
Perfect, this is confirmed fixed for me as well. Thanks!
+1. This is happening for me as well with the update to 5.3.3.
Ok, just did a test on a local installation with a large batch of dummy user accounts. The search functionality did work for the user field.
However, I noticed that field behaves differently than the others. It preloads all of the users into the select box, unlike the other fields, which only load 20 at a time. Then, more are loaded dynamically as you scroll.
That was confirmed after comparing the source of the user field with the others.
So, I could modify the other fields to load all data, but I’d prefer not to. I’d prefer to have it search/load everything only when I actually type in the search box.
Any thoughts on that?
Will do!
I can setup a quick test installation after the holiday weekend on Monday and give it a try. Thanks again for your help. Will report back here soon.
Hey Jonathan,
Thanks for your reply. I just took a look and I’m getting no JS errors in the console. Also, I verified that no other plugins are using Select2.
That triggered some other thinking though. I decided to try out the Relationship field, which has a similar search feature that does not use Select2. I am running into similar issues with that as well.
Is it possible that the Page Link, Post Object, and Relationship field all utilize the same method or similar methods that could have been changed within the last few updates? I know they were working fine a few versions ago. I’m not sure at what point it started to break.
Any thoughts on that?
Hey, I removed that updating field code immediately after and the problem persisted.
I found a random unrelated chunk of code that was causing the error. I don’t know why it is causing it though. I don’t know if it’s the unrelated code’s fault, or ACF’s fault, or some strange interaction between the two.
Any time I run wp_insert_post() or wp_update_post() on a page load that occurs within WP Admin, the issue I described shows up. When I deleted all calls to those, everything worked again. I am using them to sync a post type to an external API. Perhaps those two functions require an attachment to a special hook that I’m not using? Any thoughts on that?
