a) If exception value (e.g. all) of an argument is provided in URL, it is written to DB, and if "Pass Contextual Filters" option is used it uses other ordering compared to page without arguments, but generally it is the same list of items and same page.
b) If view arguments uses default value (e.g. from query), exception value for each argument is written to DB when arguments aren't set. In this way when one more argument is added to the view (or exceptions value is changes), ordering on the main page without arguments is lost.
Process exception value as empty (NULL) and tail empty values from arguments list, written to DB.
- Same page on different URLs "/view-page/" and "/view-page/all" shows same ordering.
- New argument could be added without ordering loss for previous argument values.
- An argument exception value could be changed without ordering loss.
No
No
In "args" DB column only active arguments are kept now. Exception values that goes before real values are kept as null, and trailing ones are ignored.
Active
2.1
Code
Attaching an actual patch, and one more that applies on top of "Pass Contextual Filters" option is broken on multiple sorts 🐛 "Pass Contextual Filters" option is broken on multiple sorts RTBC issue.
I missed the rebase point, so the last one become this issue on top of 3336466, making correct