search results heading is not rendering correctly

[AnirudhSingal91]

Expected behavior

on search for keyword "shoe" (for example), div with id = "search-results-heading" should show 3 results for shoe

Actual behavior

it instead shows 3 results for { search_query }

Steps to reproduce behavior

search for keyword "shoe" in the home page search bar

[pootle85]

Hi, I am experiencing the same behaviour, seems a bit strange that this has just happened out of the blue.

Thanks,

Neil.

[danvisionarybrands]

I can confirm the same is happening as well with all four of our stores, while no changes were made internally to any of the areas that would affect this. I was just about to review some source code to see what is going on when I figured it would be best to check Github first for other complaints. Glad to see it is not just our stores being affected.

Search Results for { search_query }

Below is the source code in our theme for the affected header that is no longer outputting the search terms...

{{{lang 'search.results.results' search_query=forms.search.query}}}

[VisionsDeveloper]

Guys,

You can resolve this issue by simply remove the single quote from the en.json file.

It's working for us.

Thanks, VD

[enkota]

All good with @VisionsDeveloper's fix, but when we have modified over 100 stores, this is not a quick fix... BC support have logged an engineering ticket with this issue, so hopefully it can be resolved server side.

I have also noticed the issue appears when changing an option set on a product at cart level too.

[danvisionarybrands]

I can confirm on our end the issue is resolved with all four of our stores. We were notified about the BC engineering ticket as well from support and it seems it has been resolved on the server side. While editing the en.json file would have sufficed, as @enkota mentioned, this issue arose on the server side so it would be ideal for BC to fix it as opposed to having to push out new theme versions for all of our stores.

[danvisionarybrands]

@enkota Confirm if you are still having the "Configure {name}" issue in the cart configurator modal as we were also affected, I reported it in issue #2128, however it seems the BC engineering ticket fixed both issues as of today.