sort_order in Configuration table insert

[torvista]

Hi,
at the risk of exposing my ignorance I have a geek question.

In the interests of cleaning up a shoddy payment module supplied by my bank (Cajastur, Spain), I have been delving into the code.
I have done the essential stuff and now I am looking for how to change the displayed order of the data entry fields in the Admin for the module.
i.e. How they are presented vertically to the user.

In all the payment modules there is something like this for the install function:

$db->Execute("insert into " . TABLE_CONFIGURATION . " (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) values ('Sort order of display.', 'MODULE_PAYMENT_AUTHORIZENET_SORT_ORDER', '0', 'Sort order of display. Lowest is displayed first.', '6', '0', now())");

My questions are,
1) what is the "sort_order" field? As you can see, here it is '0' near the end. If it has something to do with the admin order I can't figure it out as many share the same number.
2) if it has nothing to do with the order, then how DO you change the field order as shown in the admin?

thanks
Steve

[Ajeh]

1. Sort Order will be the display order of the Payment Modules or Shipping Modules or Order Total Module ...

This allows you to change the order when Editing the Module in your Zen Cart Admin ...

[DrByte]

2. Change the order in which the keys are listed in the keys() function.

[torvista]

Doh!
I should have known better than bleary posting last thing at night.

Thanks Ajeh for answering the (dumb) question I appeared to ask, but not what I really wanted to know.

I chose that execute at random and didn't notice (!) it had three references to sort order in it...

Dr.Byte you answered the original real question I had, but now just for interest, what is sort_order in these field entries?

Here you see the install options for two data field entry items that appear in admin for this module.

1) $db->Execute("insert into " . TABLE_CONFIGURATION . " (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ('Authorization Type', 'MODULE_PAYMENT_AUTHORIZENET_AUTHORIZATION_TYPE', 'Authorize', 'Do you want submitted credit card transactions to be authorized only, or captured immediately?', '6', '0', 'zen_cfg_select_option(array(\'Authorize\', \'Capture\'), ', now())");

2) $db->Execute("insert into " . TABLE_CONFIGURATION . " (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, use_function, set_function, date_added) values ('Payment Zone', 'MODULE_PAYMENT_AUTHORIZENET_ZONE', '0', 'If a zone is selected, only enable this payment method for that zone.', '6', '2', 'zen_get_zone_class_title', 'zen_cfg_pull_down_zone_classes(', now())");

They are all "0" or "2" in this module.

cc.php has 130,131,132,134,135.
Paypal.php has 0,2,3,4,5,6,7,8,18,20,22,25,73,25,71,1,72

I just don't trust anything in this module I am working on and after a lot of time on the learning curve I (now) understand everything else I have found, so this is the last bit,

thanks
Steve

[DrByte]

The sort order in the configuration keys for payment/shipping/order-total modules is irrelevant. It's part of similar infrastructure used for handling configuration values in the other config menus, and in those cases the sort order denotes the order in which they appear for editing. But for the various "modules", it's ignored entirely.

[torvista]

What a time waster!
Thanks for that,
Steve