[enoversum]

Hey Ernest,

thanks again for your effort.

So you would say that showing different fields’ content based on post type is something marginal most users won’t need?

While your hooking solution might let me specify what custom field(s) I want to display on a per-post-type basis, I would still not get only the field displayed that contains the search term – and I think the latter is something that would be interesting to a lot of people. It would be great to have the hook solution to define a default (i.e. search term is in the title or a field not activated to be shown) while the field containing the search term is being used as description so that users see the relevance by first look.

1. – thank you again and again :).
2. Why is it excluded? And will it stay that way, apart from your modification on my server? Am I the first one asking :)?

All the best

Eno

[enoversum]

Hey Ernest,

that sounds real fine, just lemme know :).

I just looked into 3), the ability to show search results and display something else but the post description, and your solution is more or less going into the right direction, but leaves a desire for modification :D. First of all, it is a bit of a hassle to include each and every possible custom field that should go into that, but mainly because I think we mean two a little different things.

When I cram in every field I want to be able to show into the little box, it just gets overloaded, like

{descriptionfield} {untertitel} {leistungen} {freitext} {textbloecke_0_block_0_text} {textbloecke_1_block_0_text} {textbloecke_2_block_0_text} {textbloecke_3_block_0_text} {textbloecke_1_block_1_text} {textbloecke_2_block_2_text}

However, this is not exactly what I was after. It’s actually two things when I look at it.

A) First and foremost, define in what fields your plugin is searching – this is already possible and happening – and show a snippet with the text highlighted so users can examine what the search result means to them, a little similar to Google search results (they not only take the meta description, but show a snippet of the content in which your search query is being hightlighted). So not every field is showing, only a snippet from the field the search text is found in.

B) This is less stressing, but still useful in that matter – determine on a per-post-type basis what (custom) field should be shown by default. By hitting in every custom field like I just did it produces a highly messy output.
And even if not, if there is no the_content present on my CPT I still get the three dots in the search results. Meaning: If I choose {descriptionfield} {custom_field1} (because on posts, the normal the_content is present, while I need ‘custom_field1’ for my CPT posts), it still displays the three dots when the ‘descriptionfield’ is empty.

By ‘default’ I mean something like searching for a CPT’s name – since the part to be shown would be the title which is there anyway, something like a snippet should still appear below it :).

I hope I am clear of what I mean? If I can be of any help, just let me know ;).

I just came across two minor additional issue when I tried out how highlighting works.

1.) So far it mostly (!) correctly highlights if I search a full word or a word that may be a partial, but ends with my search term. You can try yourself: If you search for ‘ärztliche’ on the main site the partial word is highlighted in ‘hausärztliche‘. However, if you just use ‘ärztlich’ (which is not present as a single word or at the end of a compound word on the site) it still finds the right post, but doesn’t highlight at all. It would be great to have your plugin highlight in any case.
Strange is that it seems to depend on the actual term you are using. When trying the same with ‘Bescheinigungen’ and ‘scheinigungen’, even though the latter is the last part of the word it is not being highlighted.

2.) It is great that you can filter out tags from the description, but this only seems to apply to the standard description fields, not custom fields? When you do a simple search like ‘ach’ on my main project site it shows you that still anchors and images are included, even though they had been instructed to be stripped out in the settings panel (please disregard the small/different font sizes in the search results). Can you look into that as well :)?

All the best

Eno

• This reply was modified 11 years, 6 months ago by enoversum.

[enoversum]

Update: Thanks for the comments in the search_content.class.php, it lead me to exactly what I meant – I just replaced

$obj->labels->singular_name

with

$obj->labels->name

so it takes the plural form of my post types. Still an option to rename the output of the %GROUP% variable would be awesome :).

[enoversum]

Well, as I wrote before, you have an option for the CPT on the frontend filter settings, see attachment. I could imagine something quite similar to this for the grouping feature for the frontend, adding up ‘Posts’ and ‘Pages’ since they are no CPTs. You offer to rename it in one place, so it would convenient to have it in another place as well – and it is more vital to me. Having a list of posts with a heading of ‘Post’ [singular] just doesn’t make much sense, plus I might want to completely rename a CPT on the frontend (have this on another site which so far does not use your plugin, but renames a CPT by plugin in the frontend).

[enoversum]

Will look into that later, will you make this an option for the backend settings (I know, getting crowded already ;))?

[enoversum]

Hey Ernest,

I will check out 1 and 3 myself, thank you so much, don’t really know what I was up to with the custom field filter.

As for 4. I know – but it is exactly the %GROUP% variable I’d like to customize, so on the frontend it doesn’t say “Post” or “Page” as a group heading, but “Posts” or “Pages” or anything I’d like to appear as a name for a post type. So far it only spits out the singular name of the post type.

Thanks again, I hope you stay sane with that amount of support tickets coming in :).

[enoversum]

Thanks again, awaiting your reply ;). Try out the details in the txt below, should work just fine.

[enoversum]

Hey Ernest,

if you would rather have me split my questions into single support tickets, let me know. Some of them I had already asked before.

1.) It actually now restricts search results to the current blog, that is perfect.
However, only posts and one of the two CPT I picked are searchable (post and arzt), what is missing from both sites are normal pages and another CPT I chose (dienstleistung). They are equally picked/enabled in the settings so I wouldn’t know what’s keeping them from appearing. You can try any page’s or dienstleistung’s title or content, neither site shows results.

2.) Also, I see you have implementend a ‘priority’ settings page, only I cannot choose anything there, it’s only a box of two dropdowns, and the blog picking select only shows ‘current’. Is this by design/to be finished or by mistake?

3.) And another one. I asked on another ticket I suppose if it was able to show the content of those custom fields I choose for searching inside. The search itself works, only since most do not have a normal the_content() field filled, it only shows three dots. I would love to have the user see where exactly the search term appears on the post. Didn’t I just find the option for that?

4.) As asked before, can you provide an option how each group’s heading for every single post type is being named, just as you do for ‘Show search in custom post types selectors’ within the frontend search settings options?

All the best, and hope you don’t mind 😉

Eno

[enoversum]

I do get notified, thank you :).

Did you change things on my live site? Edit: Obviously, is now working.

I didn’t get any notification on my codecanyon/Envanto account that you updated your plugin since I bought it (just checked yesterday manually and downloaded it), is this known, due to Envanto or probably something on my side? Is there a way to get a comfortable dashboard notification as with some of my other premium plugins I bought so far?

Thanks again ;).

• This reply was modified 11 years, 6 months ago by enoversum.

[enoversum]

Hey Ernest,

I was just wondering you didn’t care about my question, haha :D.

How do I best proceed? You may remember you did log into my installation and created a test form while it was a single blog. After that I turned it into a multisite. Now, not changing the form and just placing the same shortcode into my second site only gives me the same layout (as intended/changed only via CSS) and the same results, only from the main blog. I checked and didn’t see any blogs to choose from in the backend, didn’t you incorporate the fix in the latest version? If there are blogs available, how do I proceed so that the same form can be used on both blogs, but only show the current blog’s search results?

Thanks in advance

Eno

[enoversum]

Hey Ernest,

I know you are quite busy, can you help out on this one nonetheless? To cut it short, I use the same shortcode on the mother and a ‘child’ site, but it only displays results from the mother site, even on the ‘child’ site. Shouldn’t the plugin only show results from each site?

[enoversum]

Hey Ernest,

no problem you deleted the search, I had tried myself a new search instance, but it didn’t help. As for the database/options thing, you’re still referring to your own plugin (or do you mean my options page in the backend)?

However, this version works well, will see how it does when I configure it to my needs.

Will see for the CSS thingy then ;). Didn’t find that it conflicted with my theme, so thanks a lot for the extra work!!!

Any update on the relevance sorting thing I have been getting on your nerves so much :)?

Best

Eno

[Author]

Posts