Well, I don’t really know how other people use this plugin ??
The support for the GET parameter orderby
was part of this plugin before I showed up as maintainer. I can imagine people building custom stuff with that GET parameter to be able to sort categories and custom taxonomies in al kinds of ways.
And we don’t all use WooCommerce ?? That is just one of the 100,000 plugins available. If this sorting plugin was single-aimed at WooCommerce that might be a point, but even then people might have built custom code around this GET parameter.
So simply, I do not dare to remove that check. In the case of people that built custom term lists which can be sorted with a similar dropdown that changes the order of terms, I prefer not to break that.
I do think that preserving the default behaviour would be a good thing, and optionally deviating from that default would be a nice option. It would only require some simple PHP code that can be documented in the FAQ.
The tricky thing is ofcourse that an orderby
GET parameter is very ambigious. Is it about post order, term order, user order, something else?
It might be an option to break backwards compatibility and only check for a term_orderby
GET parameter. But since this question is now the first I see in I think 8 years, I would prefer adding an exception to this usecase and not one supported for more than 8 years.