I noticed today on a website recently updated to 1.4.14 that the evoSearch placeholders in the statTpl, noResult parameters and Search Form Input are not output if the PHx plugin is enabled.
(This site uses phx:outer with MultiTV for displaying product data and doesn't display anything with PHx disabled and Modifiers enabled. So for now needs to retain PHx.)
1 &statTpl=`<p>[+stat_total+] results found for "<span class="evoSearch_highlight">[+stat_request+]</span>"</p>`
2 &noResult=`<p>There were no results for "<span class="evoSearch_highlight">[+stat_request+]</span>". Please try a different term.</p>`
3 <div><input type="text" name="search" title="Enter Search Terms" placeholder="Search here..." value="[+stat_request+]" required /></div>
If PHx enabled, I get the following:
1 statTpl output = results found for ""
2 noResult output = There were no results for "". Please try a different term.
3 search form field = no search string (empty)
If PHx disabled, I get:
1 statTpl output = 37 results found for "blah"
2 noResult output = There were no results for "dwdwdwd". Please try a different term.
3 search form field = the search string eg dwdwdwd
Presuming this is a bug??
NB. I tried the &disablePHx=
1 parameter that can be used in DLMenu snippet calls when there are PHx issues but that doesn't make a difference in this instance.
Anyone know of an evoSearch workaround to still display parameters when PHx plugin is enabled??