Skip Navigation

[Resolved] Dashboard CPT Search Functionality Returning All CPTs

This support ticket is created 6 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by Christian Cox 6 years, 4 months ago.

Assisted by: Christian Cox.

Author
Posts
#949200
Screen Shot 2018-07-17 at 10.41.29 AM.jpg

I am trying to: When in the back-end dashboard and I navigate to a CPT, like Access Cards, and use the search functionality in the top right-hand corner, it brings back results not only within that CPT but any CPT. I would not expect that other CPTs would be returned.

Link to a page where the issue can be seen: hidden link

#949322

Hi, that's unusual and I'm not able to replicate it on my local environment. Can you try the following troubleshooting steps to help narrow down the issue?
- Temporarily deactivate all plugins except Types and activate a default theme like Twenty Seventeen. If you need to enable a Maintenance Mode plugin while testing, that's fine.
- Test the same search again. If the problem is resolved, reactivate your theme and plugins one by one until the problem returns.
- If the problem was not resolved, I'll need to take a closer look. I'll need login credentials for your wp-admin area. Private reply fields are active here so you can share securely.

#950613

I found the plugin in causing the issue, Memphis Documents Library. Unfortunately it's one that I need.

#951440

I understand, feel free to reopen this ticket if you would like for us to investigate this issue as a compatibility problem. It might be possible for us to collaborate with the plugin authors to work out a solution.