-
Alice Heaton authored
Re-introduce the per-row drop down to update each record's category as well as the mirrored buttons at the bottom of the page. This means that we have a single form that can either do a batch update, or an update of values set per row. The different action is determined by the submit button that was used - which is always named 'action'. Because we have a mirrored select drop down for the batch action, we need to know which one to take into account - so the value of the submit button indiciates which one was clicked, of the form <action>-<placement> (eg. save-top) and the name of mirrored inputs indidicate where they are located, of the form <name>-<placement> (eg. batchaction-bottom). The ViewItems class has a static method to find the active placement and rename the parameters accordingly. Some of the old code was re-introduced, though some of it was refactored (eg. what used to be get_categories, to fetch each row's selected category, has been moved to ItemTable to parallel get_selected, and is now named get_row_select_value (it's a more generic version, looking at the future when we'll update the region with the same mechanism.)
Alice Heaton authoredRe-introduce the per-row drop down to update each record's category as well as the mirrored buttons at the bottom of the page. This means that we have a single form that can either do a batch update, or an update of values set per row. The different action is determined by the submit button that was used - which is always named 'action'. Because we have a mirrored select drop down for the batch action, we need to know which one to take into account - so the value of the submit button indiciates which one was clicked, of the form <action>-<placement> (eg. save-top) and the name of mirrored inputs indidicate where they are located, of the form <name>-<placement> (eg. batchaction-bottom). The ViewItems class has a static method to find the active placement and rename the parameters accordingly. Some of the old code was re-introduced, though some of it was refactored (eg. what used to be get_categories, to fetch each row's selected category, has been moved to ItemTable to parallel get_selected, and is now named get_row_select_value (it's a more generic version, looking at the future when we'll update the region with the same mechanism.)