This is very curious, as basic cases are working for me. Can you please
submit a series of steps to repro the error?
On Fri, Mar 30, 2018 at 9:44 AM, Jason Stephenson <
<email address hidden>> wrote:
> I tested this and in the most basic case, I'm still seeing ARRAY(...) in
> the search box when placing a hold after advanced search. I'm removing
> the pullrequest tag and assigning it back to Dan Pearl.
>
> ** Changed in: evergreen/3.0
> Assignee: Jason Stephenson (jstephenson) => (unassigned)
>
> ** Tags removed: pullrequest
>
> ** Changed in: evergreen
> Assignee: (unassigned) => Dan Pearl (dpearl)
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: LP_Mail
> https://bugs.launchpad.net/bugs/1732591
>
> Title:
> Array error appears in search box while placing hold after advanced
> search
>
> Status in Evergreen:
> Confirmed
> Status in Evergreen 2.12 series:
> Won't Fix
> Status in Evergreen 3.0 series:
> Confirmed
>
> Bug description:
> Evergreen version: 2.12 and 3.0
>
> In bug 1671635, we added some hidden fields for qtype, query, and locg
> to the place hold page so that a user could edit their search from the
> searchbar on the holds confirmation page. While this works well when
> the user starts off in a basic search, those parameters aren't applied
> correctly if the search began on the advanced search page.
>
> After clicking 'place hold', we end up with a URL that looks like
> this:
>
> https://mlnc1.noblenet.org/eg/opac/place_hold?bool=and;bool=
> and;bool=and;qtype=keyword;qtype=title;qtype=author;
> contains=contains;contains=contains;contains=contains;
> query=concerto;query=;query=;_adv=1;detail_record_view=0;
> locg=1;pubdate=is;hold_source_page=%2Feg%2Fopac%2Fresults%
> 3Fbool%3Dand%3Bbool%3Dand%3Bbool%3Dand%3Bqtype%3Dkeyword%3Bqtype%3Dtitle%
> 3Bqtype%3Dauthor%3Bcontains%3Dcontains%3Bcontains%3Dcontains%3Bcontains%
> 3Dcontains%3Bquery%3Dconcerto%3Bquery%3D%3Bquery%3D%3B_adv%
> 3D1%3Bdetail_record_view%3D0%3Blocg%3D1%3Bpubdate%3Dis;
> hold_type=T;hold_target=2
>
> The user will see an ugly array error in the search bar.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1732591/+subscriptions
>
This is very curious, as basic cases are working for me. Can you please
submit a series of steps to repro the error?
On Fri, Mar 30, 2018 at 9:44 AM, Jason Stephenson <
<email address hidden>> wrote:
> I tested this and in the most basic case, I'm still seeing ARRAY(...) in /bugs.launchpad .net/bugs/ 1732591 /mlnc1. noblenet. org/eg/ opac/place_ hold?bool= and;bool= and;qtype= keyword; qtype=title; qtype=author; contains; contains= contains; contains= contains; query=; query=; _adv=1; detail_ record_ view=0; pubdate= is;hold_ source_ page=%2Feg% 2Fopac% 2Fresults% 3Dand%3Bbool% 3Dand%3Bbool% 3Dand%3Bqtype% 3Dkeyword% 3Bqtype% 3Dtitle% 3Dauthor% 3Bcontains% 3Dcontains% 3Bcontains% 3Dcontains% 3Bcontains% 3Bquery% 3Dconcerto% 3Bquery% 3D%3Bquery% 3D%3B_adv% record_ view%3D0% 3Blocg% 3D1%3Bpubdate% 3Dis; T;hold_ target= 2 /bugs.launchpad .net/evergreen/ +bug/1732591/ +subscriptions
> the search box when placing a hold after advanced search. I'm removing
> the pullrequest tag and assigning it back to Dan Pearl.
>
> ** Changed in: evergreen/3.0
> Assignee: Jason Stephenson (jstephenson) => (unassigned)
>
> ** Tags removed: pullrequest
>
> ** Changed in: evergreen
> Assignee: (unassigned) => Dan Pearl (dpearl)
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: LP_Mail
> https:/
>
> Title:
> Array error appears in search box while placing hold after advanced
> search
>
> Status in Evergreen:
> Confirmed
> Status in Evergreen 2.12 series:
> Won't Fix
> Status in Evergreen 3.0 series:
> Confirmed
>
> Bug description:
> Evergreen version: 2.12 and 3.0
>
> In bug 1671635, we added some hidden fields for qtype, query, and locg
> to the place hold page so that a user could edit their search from the
> searchbar on the holds confirmation page. While this works well when
> the user starts off in a basic search, those parameters aren't applied
> correctly if the search began on the advanced search page.
>
> After clicking 'place hold', we end up with a URL that looks like
> this:
>
> https:/
> and;bool=
> contains=
> query=concerto;
> locg=1;
> 3Fbool%
> 3Bqtype%
> 3Dcontains%
> 3D1%3Bdetail_
> hold_type=
>
> The user will see an ugly array error in the search bar.
>
> To manage notifications about this bug go to:
> https:/
>