Forum Replies Created
-
AuthorPosts
-
nazar
ParticipantYeah, I’m aware of Priorities, but this only works for post and CPTs.
I was mainly asking about taxonomy terms since these contain locations info in my case.
Anyway, I hear you 🙂 I’ll keep experimenting myself.February 10, 2017 at 11:53 am in reply to: Bug: minimal number of typed characters to trigger live search #11880nazar
ParticipantYep, you’re right. Definitely some food for thoughts here, thanks.
Will definitely check CloudFlare in depth too.February 9, 2017 at 10:02 pm in reply to: Loader and 'close' button position with disabled magnifier #11875nazar
ParticipantAbsolutely, that’s what I did. With the only change – I needed to restyle this piece in a particular form only (I have several ASP forms).
So my CSS ended up like this:
[code]
#ajaxsearchpro4_1 > .probox > .proclose svg {
// styling here
}
[/code]Thanks for your attention to this.
Edit: no idea how to escape “>” in the code here 🙂 Those “>” should be “>”
-
This reply was modified 9 years, 3 months ago by
nazar.
nazar
ParticipantWow, I can’t believe I didn’t notice this.
Thanks a bunch, you rock!
February 9, 2017 at 8:57 pm in reply to: Bug: minimal number of typed characters to trigger live search #11870nazar
ParticipantIt would be great to have this fix included in the release sooner than later because I can see the current behavior as a potential abuse magnet.
Someone or something (bot) bombarding a bigger website with 1-2 letters search queries. Doesn’t sound good to me 😉
And yes, I realize that it will eventually hit the results limit, but in some cases it’s necessary to have really high limits (a different subject indeed, I’ll come back with this in a separate topic).I started looking for some ways to prevent search abuse (e.g cap speed at X search queries per minute per user) or actually have a ‘real’ hard limit on the minimal character count that will ignore spaces, commas and so on.
Not meaning to push you with this in any way, but the thing may become a real problem for big and competitive websites. I’ll share any valuable info I find on this.nazar
ParticipantYou cannot access this content.
February 8, 2017 at 9:07 pm in reply to: Loader and 'close' button position with disabled magnifier #11859nazar
ParticipantErnest,
A somewhat related small “bug”.
There’s no option to style the close button, so it’ll always be round, black with white fill and shadow. Of course, I can target it with CSS and restyle it easily, but maybe something you’ll want to consider adding in plugin options 😉Cheers.
nazar
ParticipantYou cannot access this content.
nazar
ParticipantYou cannot access this content.
nazar
ParticipantYou cannot access this content.
June 21, 2016 at 1:58 pm in reply to: Loader and 'close' button position with disabled magnifier #9171nazar
ParticipantNo prob 😉
nazar
ParticipantOops, looks like I skipped that disclaimer 🙂 Sorry!
P.S. Would be super-cool to have that work with Grouping though.
nazar
ParticipantAh, got it.
We’ll wait for the new version, no big deal.
Thanks for the heads-up.nazar
ParticipantHiya Ernest,
Wow, thanks for that!
Now I can also see what I was doing wrong in my code 🙂Yeah, ACF and their wp_options approach…
That’s the only reason I don’t use ACF. You’re right, they didn’t switch to term meta yet, not sure if it’s on their roadmap either.
People do request the switch – https://support.advancedcustomfields.com/forums/topic/how-to-use-wp-term-meta-on-acf-the-easy-way/ – but I’m guessing they have to either maintain backwards compatibility or build a migration routine (or even both). None of those is a trivial task…Thanks again for your help.
nazar
ParticipantHiya Ernest,
I believe, the most ‘standard’ way is the native term meta: https://www.smashingmagazine.com/2015/12/how-to-use-term-meta-data-in-wordpress/
I usually use either that (yep, coding everything manually) or Pods (when my customers need a GUI).I checked your code snippets in those threads and I can see different approach depending on plugins/functions used, however, I’m kinda stuck with writing a proper filter for my case.
In my current setup I have the following combination of search sources: 1 CPT, 2 custom taxonomies, 1 custom field.
In plain English: Listing (CPT), Listing Category and Listing Region (hierarchical taxonomies), zip code (CPT custom field).Now, search results will display thumbnails for listings (CPT match), taxonomy name (taxonomy match), and thumbnails for listings again (custom field match).
So can I ‘assign’ default search results images for those taxonomies? I prefer a simple static image for each taxonomy for now.
Almost like https://www.daysoutwithkids.com/ do that, if we assume that attraction and location are taxonomies.And just in case you know the answer 🙂
I might add images and other term meta to taxonomies using Pods – e.g. flag icons and state abbreviations for Regions, some icons for Categories, etc.
Do you know how to make these appear in search results? E.g. a flag icon near country name, state abbreviation after state name, etc?Also, while I’m here…
Chances are we’ll be adding another CPT – Celebrities, so we’ll end up with two CPTs in search sources.
In that case we’ll want to display a standard image in search results for every CPT (exactly like https://www.daysoutwithkids.com/ if we assume that attraction and location are CPTs).
Is there a neat way to do this?Thanks!
-
This reply was modified 9 years, 3 months ago by
-
AuthorPosts