When items search is with a custom field using authorised values, html TT filter is breaking the JS, it should use raw.
Created attachment 87071 [details] [review] Bug 22596: use raw TT filter in items search with custom field When items search is with a custom field using authorised values, html TT filter is breaking the JS, it should use raw. Test plan : 1) Go to Administration > Item search fields 2) Define a search field with an authorised values category 3) Go to items search 4) Use the "New field" link 5) Check use of custom field is OK
Created attachment 87123 [details] [review] Bug 22596: use raw TT filter in items search with custom field When items search is with a custom field using authorised values, html TT filter is breaking the JS, it should use raw. Test plan : 1) Go to Administration > Item search fields 2) Define a search field with an authorised values category 3) Go to items search 4) Use the "New field" link 5) Check use of custom field is OK Signed-off-by: Liz Rea <wizzyrea@gmail.com>
Created attachment 87170 [details] [review] Bug 22596: use raw TT filter in items search with custom field When items search is with a custom field using authorised values, html TT filter is breaking the JS, it should use raw. Test plan : 1) Go to Administration > Item search fields 2) Define a search field with an authorised values category 3) Go to items search 4) Use the "New field" link 5) Check use of custom field is OK Signed-off-by: Liz Rea <wizzyrea@gmail.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Awesome work all! Pushed to master for 19.05
Pushed to 18.11.x for 18.11.05
wont backport to 18.05.x series
IMO it would have been better to encode TT-side (see TT plugin To.json), raw must be avoided as much as possible.
(In reply to Jonathan Druart from comment #7) > IMO it would have been better to encode TT-side (see TT plugin To.json), raw > must be avoided as much as possible. This must be addressed, we should not use $raw when can be avoided.