-
updated info-file according to new 7.x requirements: Module .info files must now specify all loadable code files explicitly.
-
copied changes from release 6.x-1.1
-
updated changelog
-
added missing verb
-
#631858 by tuffnatty: nodeorder.js sometimes enables wrong submit button
-
#613030 by lportela: PostgreSQL support; make sure all columns used in ORDER-clause occur in SELECT-clause as well
-
#499326: removed redirect althogether to make sure the behavior is consisten both when coming via the taxonomy administration pages or via the term-page
-
#499326: behaviour of submitting the ordering form has been made consistent with other modules like taxonomy and blocks; upon submitting the form the user is "redirected" to the ordering form (i.e. the user stays on the ordering form and sees the modified ordering)
-
rename nodeorder_get_weight to more descriptive nodeorder_get_term_min_max use TRUE and FALSE instead of 1 and 0
-
merged changed from 6.x-1.x branch #242077 by pvanderspek: make order nodes tab at admin/content/taxonomy/% optional #259267 by pvanderspek: cache the results of nodeorder_can_be_ordered and nodeorder_orderable_tids #259267 by pvanderspek: cache the results of nodeorder_can_be_ordered and nodeorder_orderable_tids and nodeorder_term_can_be_ordered #107860 by marcp, pvanderspek: nodeorder should not show move up / down link when it does not apply