Currently there are several places in qbank_columnsortorder with hard-coded special cases for qbank_customfields, as it may provide columns with arbitrary names that don't relate to an actual class in the code. These cases parse the column's unique name from the provided "class".

This logic should be moved inside the customfields plugin, such that that any plugin can define it's own method for returning the unique identifier of a column.