Pro 4.2 - Terms in custom search page (possible bug)

I’m building a custom search results page.

Not sure what is up here but if I create a looper that has another looper for my terms the terms show in the builder but not on the front-end.

This set up works on archive pages but not for search results.

I’ve also tried using your dynamic element as a test with the same result. The term displays in the builder but is empty on the front-end.

Hi @urchindesign,

I’ve tried this out but can’t seem to reproduce it. Here’s what I’ve done:

  • Create a new Archive Layout and used one of the Starter Templates
  • Place a Terms Minimal directly after the Post Title
  • Change the Terms provider type to “Current Post Terms”
  • Assigned the Layout to Search

In the builder and front end I’m seeing the terms of each respective post right below the title. Let me know if you can think of any differences in our setup that I can try.

I’ll take a look over the weekend. Mine was working in an archive layout but not in the search results. In the builder is viable but on the front-end it was just an entity button. Jenny out any conditions on it.

I first used my own one and then I tried one of the prebuilt elements with the same results.

Gotcha, let me know whenever you have time. I tested both in an archive and search results and it was the same formatting.

Just one question. How do we preview the search results in the builder. If I choose search results from the preview I get an error about no suitable preview and a 404 page.

1 Like

Very strange.The pre-built meta line is working which wasn’t working before. Previously it was showing in the builder but not on the front-end.

What I figured out for the one I built was that I had created the looper provider but hadn’t set the headline to be a consumer. What is strange though is on the archive page the category displayed in both the builder and the front-end even though I hadn’t set the item as the consumer. On the search results the item displayed in the builder but not on the front-end.

This was a mistake on my side but I would say it should work consistently and shouldn’t show anywhere if the consumer is not set.

Hi @urchindesign,

I don’t think it was previously possible to actually preview on specific search results. Probably why we had some discrepancies here. I’ve made some changes in the next beta to allow setting a search term when previewing. When you choose “Search Results” it will reveal a text input now.

3 Likes