<br><br><div class="gmail_quote">On Mon, Jul 20, 2009 at 8:36 AM, Bill Ott <span dir="ltr"><<a href="mailto:bott@grpl.org">bott@grpl.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Mike Rylander said the following on 07/15/2009 08:21 PM:<div class="im"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The advanced search form, being (partly) static, gets populated by the<br>
browser when you hit back (that's the first set). However, the code<br>
also parses the URL to populate the search form when coming from a<br>
basic search result. Thus, double- (or triple-) population. As for a<br>
fix, there are a couple ways I can think of, but none are what I'd<br>
call Good(tm). We could conditionally clear the search form if we're<br>
using url data, or built the form dynamically ...<br>
<br>
</blockquote>
<br>
<br></div>
This is a bit of a Kludge(tm), but this seems to do the trick.<br>
</blockquote><div><br><br>Tested and applied to 1.6+. Thanks, Bill.<br><br>-b <br></div></div><br>-- <br>Bill Erickson<br>| VP, Software Development & Integration<br>| Equinox Software, Inc. / The Evergreen Experts<br>
| phone: 877-OPEN-ILS (673-6457)<br>| email: <a href="mailto:erickson@esilibrary.com">erickson@esilibrary.com</a><br>| web: <a href="http://esilibrary.com">http://esilibrary.com</a><br>