Jordan L authored Jul 10, 2014 and Dieuwe de Boer committed Jul 10, 2014

permissions.

#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)

use TRUE and FALSE instead of 1 and 0

#259267 by pvanderspek: cache the results of nodeorder_can_be_ordered and nodeorder_orderable_tids and nodeorder_term_can_be_ordered

nodeorder_link_to_ordering_page is turned off.

Moved nodeorder_can_be_ordered() call into each case of the switch in
nodeorder_nodeapi() to keep from calling it during 'view' and other ops.

renamed some functions

prevent weight_in_tid of 0 to be restored

it might not always work correctly depending on the specific setup

weight_in_tid is set ot 0 when a vocabulary is no longer orderable

make sure that initializing weight_in_tid happens in a single transaction

node_load is no longer used to add a list of orderable tids, so the required functionality has been added here

see also the comments in the code, but I added an additional submit-handler which takes care of saving the orderable-setting

fixed a bug where hook_taxonomy was called for type vocabulary after editing a term; this would then disable the orderable setting for the vocabulary

use st() instead of t() during the install process, when database, theme, and localization system is possibly not yet available.

change case 'load' to case 'presave' in nodeorder_nodeapi, because the elements added while loading a node aren't passed to the node-edit page; caching the existing weight_in_tid values just before saving makes sure taxonomy didn't have a chance to delete rows in term_node-table yet, and still allows for passing values to case 'update' as opposed to when case 'load' is used