Plugin Author
jon
(@adiant)
I’ll look at that right away. I did test the plugin with the Version 4 betas of WordPress, but never tried out Search, as it never occurred to me that they would be “related”.
I’ll respond here as soon as I know anything.
As always, I appreciate knowing when people find things that aren’t working, so I can fix them.
Well, thank you for caring! If you think it might just be something quirky with my setup, please let me know as well.
Plugin Author
jon
(@adiant)
On my Test System, I see this behaviour only on individual Sites (i.e. – not on the Network Admin) when I’m on the Installed Plugins Admin panel and trying to use the Search field to find one one of the installed plugins.
This is definitely a problem that I will investigate and fix ASAP, but I did want to make sure that this is the problem you found, not some other problem that I’m not aware of.
Thanks for your help on this.
Yup. Exact same thing I’m sure. I network activated it, but didn’t test behavior on network admin. I only noticed this reviewing child sites for network activated plugins. It was still super helpful sorting through a conflict, and I tested disabling it and it brought child plugin searches right back.
Plugin Author
jon
(@adiant)
Thank you for confirming this.
I’ve now had a chance to go through the code and see that I’ve got a bucketful of code to adapt (from WordPress Core code) and add to make this work. All of which translates into me having a new version of the plugin with this fixed within 48 hours as I’ve got some major commitments over the next 24 hours.
I’ll also post here when the new version has been released.
Plugin Author
jon
(@adiant)
Version 3.1.1 is now available to address this problem.
Please let me know if you run into any other issues.