OLD Super Orders 2.0 (See v3.0 thread instead)

[BlindSide]

This question is probably for Blindside...
Is there a reason why super_invoice.php and super_packingslip.php use stylesheet.css and NOT super_stylesheet.css (or both)??
Super_stylesheet.css includes classes like .invoiceHeader which seems relevent.

The super_stylesheet.css was designed to incorporate new CSS definitions that were not available int eh standard CSS. I still use Zen's stock stylesheet for a lot of things throughout the contrib.

Does Super Oder 2.0 support multi-language ? because some error message apears when i try to commit some change with "The payment type" Module.

Yes it definitely does, you just need to create the necessary language file and match my defines. What error are you seeing exactly? Your description kind of confused me.

To the best of my experience Super Orders has NO connection to your credit card processing gateway or PayPal. It gets all it's information from your SQL database. If the card processing module stores information returned from the gateway (like PayPal IPN) then you will have it, but SO does not initiate transactions changes.

What I do is set my card processing gateway, and also PayPal, to do AUTHORIZE, not capture of the funds. That way the amount the customer agreed to pay is held in a queue. When I ship, I go to the gateway and move the transaction from the queue to the batch to capture the funds. That way I can make corrections in the amount for back ordered items, etc. Each payment processor has different rules, but VISA says you must ship within 24 hours after capturing the funds. I think PayPal allows you to increase the charges to 115% of the original authorization. But the short answer is you have to process the payments separate from Super Orders.

Maury is absolutely right, coolboy, Super Orders does nothing with actual gateways. The infrastructure is not there in the admin (yet) to adequately support admin-side payment processing. These are simply for your records, however they DO look at your payment tables at checkout to gather the necessary information.

UPDATE FOR ALL
Latest version is pretty much boxed up and ready to ship, with the exception of one very important piece, the installer. I'm not going to do a simple SQL file again this time, because so many of the install issues were based around users having to run the file more than once for various reasons. But I can't half-arse it either; we all know that would be an even bigger disaster. So it's all about finding the time to get it done and into your hands. Sucks, I know. Sit tight!