Hi Ernest,
I’m sorry it took me a full week to get back to you! I wanted to respond earlier, but I’ve been deep in multiple projects here as usual.
Attachment Search / Filter for Default Post-Format
I know this wasn’t your preferred solution, but it worked! If you ever think of a better method to accomplish the same thing just let me know.
I just installed this filter and tested it pretty thoroughly. As far as I can tell this is working no matter what combination of post-format options I choose. I tested just about everything you could think of. Here are a few examples I tested for:
Selecting default post-format by itself
Selecting default post-format in combination with one other post-format
Selecting default post-format in combination with multiple other post-formats
Selecting one post-format other than the default
Selecting multiple post-formats other than default
Selecting no post-formats at all
That last one (selecting no post-formats) was a good test, as this produced no search results. Prior to this fix I would have seen the default post-format in the results when nothing was selected.
I do understand, and the issue is that that term does not actually exist – and it messes up the whole logic. If you think about it, the search is instructed to exclude items that does not belong to any of the taxonomy terms, but again somehow include the ones that does not belong anywhere either. There is no way of having both within a single query. This feature is something I have to maintain (single query), as adding/removing results after the completed query (within the core) would be a complete disaster.
Are post-formats a taxonomy term? While I don’t completely understand the mechanics of this, I get the basic idea. I also agree with you that having a single query makes the most sense. We certainly don’t want to harm the search because of this one “hole” in the logic.
The bottom line is that your filter solution works. You managed to get this all done for me. We have added the ability to filter the default post-format, took care of the default post-format showing up in results when it shouldn’t, and this now all works simultaneously with the ability to use attachment results.
Bravo! =)
…..
Intermittent Bug With Number of Search Result Columns (Cards)
Unfortunately no, and there are no other reports of it either for some reason. May I ask which browser are you testing this on, and your screen resolution? Thank you!
Yieks. I hope it isn’t one of our scripts or custom configurations that is causing this. Unfortunately this issue is still here and very much annoying.
I use Chrome for testing and my screen resolution is 1920 x 1200.
I have seen this problem happening on my mobile devices too however, such as on my iPad Pro and my iPhone 7 Plus. I don’t believe this has anything to do with my browser or the resolution. I think it’s script related.
I’m open to any ideas you have to test this and narrow down the cause. I can also tell you that this issue is fairly new. It started happening a few weeks ago. So it’s likely the result of an update. There’s probably a bug or some conflict occurring.
…..
Featured Image Source Size Not Working in All Situations
Looking at the source, this is going to be an issue with the plugin code. I see it is missing the cache section. I will fix this for the upcoming release.
Please keep in mind that I am not using the image caching function. I don’t know if that is related to the problem.
This issue is affecting our attachment and tag result images. It’s not affecting our category result images because we’re using a filter for those to bring up specific images we made.
If this is an easy fix on your side it will be one less thing for us to worry about here.
…..
– Date Filter Bug
– Linking Attachment Search Results to Parent (Linked) Posts (Core Integration)
– Customizable Header in Settings Screen Date Filters
I’m just listing these here so we don’t forget about them… 😉
…..
You and I have made a lot of progress these past weeks with refinements and corrections. I continue to be so impressed by your commitment to this plugin and helping me in particular. All I can keep saying is thank you!
~ Michael