Super Orders v3.0 Support Thread (for ZC v1.3.9)

[DivaVocals]

Hmmm...........is this not as easy as I was thinking? I know I've been working on a solution to no avail.

Yep looked at this earlier today.. I'm stumped too..

[DivaVocals]

Hmmm...........is this not as easy as I was thinking? I know I've been working on a solution to no avail.

The issue you are having is that the sort order of the super_invoice.php and super_packinslips.php are not controlled in these files (and the Super Orders versions work EXACTLY like their default cousins)

Try searching the forum for:
Search: Keyword(s): sort, packingslip, model

I found three threads that look promising.. Good luck..

[Get Em Fast]

Ahhh...........better key words.............that's all I needed. Thanks Diva!

Anyway, if anybody else ever needed this done, Admin/classes/order.php, find
line 121 and change to:

order by products_model

[DivaVocals]

Ahhh...........better key words.............that's all I needed. Thanks Diva!

Anyway, if anybody else ever needed this done, Admin/classes/order.php, find
line 121 and change to:

order by products_model

You are very welcome..

[DivaVocals]

So now that I looked at the mod I THINK you are using (there are several PO add-ons), I don't completely understand your question..

The workflow supported by Super Orders' currently included PO module is the standard practice used by most businesses who issue POs and businesses who accept POs..

1. Invoice/Estimate received
2. Invoice/Estimate is routed to customer's accounting department
3. Accounting issues PO
4. Customer provides PO data to vendor
5. Vendor processes the order
6. Vendor bill customer

In the standard flow, vendors do not receive POs until AFTER an order has been placed. The reason is simple. Their customers generally need to get the final total and an invoice/estimate from the vendor that they will route to their accounting department BEFORE issuing a PO to a vendor. (unless it is a blanket PO being issued - meaning it will be applied to multiple invoices until the PO is out of funds, and a new blanket PO will be issued).

Your workflow assumes that the amount of the estimate is known BEFORE the order is placed.. This is not a standard accounting workflow with regards to POs and their use in MOST businesses.

However, the add-on I THINK you are using captures PO numbers at checkout which seems to accommodate your desired workflow.. So I'm not sure why you think the PO module that comes with Super Orders should be updated to have the same functionality?? (capture PO numbers at checkout??)

It seems that both workflows need to be supported and there are already TWO payment modules which handle POs both BEFORE and AFTER the order is placed..

Haven't looked at this, and if the current PO module that comes with Super Orders is not capturing POs at checkout time, then I'm sure it could be done. Off the top of my head (I'm at work) how Super Orders links the P.O. to payments is what MIGHT (again I haven't looked at this yet..) make this change well over my paygrade to look into.

Remember that Super Orders was a custom module Blindside developed for HIS client. They may not have required the collection of PO numbers (if this is indeed how this works) at checkout, and instead entered them in after the order was placed.

Once they received payment, Super Orders allowed them (at the time they create the Super Orders payment record) to link the PO to the payment (or payments).

Sounds like what you REALLY want is the ability to automate entering the PO record to the Super Orders IF you are using the PO add-on you currently have in place.. (Similar to the automated Super Orders payment entry for credit card payments or PayPal orders)

This is VERY useful functionality that should be retained if a change is required to achieve what you are asking for..

Hey DivaVocals,

I see that you have a Purchase Order feature in SuperOrders. Was wondering if it would be possible to put this into the checkout process.

We've been using the Purchase Order contrib to do this. For us, our customers know the PO at time of order submission, and having that available at checkout is really handy.

From what I see of SO3, you would have to enter the PO from within the admin as an additional step.

Would it involve much editing to add PO to checkout in SO3?

Thanks,
cj

[cjcraven]

Server OS: Linux 2.6.35.8-nx
PHP Version: 5.2.17 (Zend: 2.2.0)
Database: MySQL 4.1.22-standard-log
Zen Cart 1.3.9h
Database Patch Level: 1.3.9h
v1.3.9h [2011-03-18 22:41:21] (Fresh Installation)
v1.3.9h [2011-03-18 22:41:21] (Fresh Installation)
Super Orders 3.0
Language English/Japanese

I installed successfully and am pleased but note two issues.

1) Manage Payment Types
This displays in English but does not in Japanese. The English side allows me to enter both languages. Not sure why it does not display when admin is in Japanese language.

2) Clicking the "Print" button in the "Orders Listing" page results in a new blank window being opened. No data appears in the new window.

Craig

[DivaVocals]

Additinal language support for payment types does not work (never has).. No idea when this will be addressed as I understand WHAT it does, but not how to fix it.. I do have a fairly decent woraround included in the upcoming release..

As for the data sheet issue, there is a fix posted in this support thread.. Please do a search in this support thread to locate this fix.

Server OS: Linux 2.6.35.8-nx
PHP Version: 5.2.17 (Zend: 2.2.0)
Database: MySQL 4.1.22-standard-log
Zen Cart 1.3.9h
Database Patch Level: 1.3.9h
v1.3.9h [2011-03-18 22:41:21] (Fresh Installation)
v1.3.9h [2011-03-18 22:41:21] (Fresh Installation)
Super Orders 3.0
Language English/Japanese

I installed successfully and am pleased but note two issues.

1) Manage Payment Types
This displays in English but does not in Japanese. The English side allows me to enter both languages. Not sure why it does not display when admin is in Japanese language.

2) Clicking the "Print" button in the "Orders Listing" page results in a new blank window being opened. No data appears in the new window.

Craig

Posted via Mobile Device

[cjcraven]

Additinal language support for payment types does not work (never has).. No idea when this will be addressed as I understand WHAT it does, but not how to fix it.. I do have a fairly decent woraround included in the upcoming release..

As for the data sheet issue, there is a fix posted in this support thread.. Please do a search in this support thread to locate this fix.


Posted via Mobile Device

Thanks for the info. Couple of other things I noticed in the Configuration of Super Orders. 4 settings, Auto Comments - Payments, Auto Comments - P.O. Payment, Auto Comments - Purchase Order, and Auto Comments - Refund, do not have settings for other languages. If you change the wording in one language then all the other languages will use the same text.

[DivaVocals]

Thanks for the info. Couple of other things I noticed in the Configuration of Super Orders. 4 settings, Auto Comments - Payments, Auto Comments - P.O. Payment, Auto Comments - Purchase Order, and Auto Comments - Refund, do not have settings for other languages. If you change the wording in one language then all the other languages will use the same text.

Super Orders is based on a custom module written for a US client. Super Orders 3 is based on this original code with improvements as noted in the readme.. Hence support for additional languages is lacking in MANY areas of the add-on.. ALL of these areas would required re-writes to support additional languages.. These re-writes are over my paygrade to tackle.. But it's open source and if a community member were to tackle this, and be willing to share it, I'd be happy to add it to the codebase..

[Design75]

So it's time I contributed something to this magnificent project. I have made some code changes to make the invoice multilingual.

in YOUR_ADMIN_FOLDER\includes\super_invoice find rule 268

<?php
  for ($i = 0, $n = sizeof($order->totals); $i < $n; $i++) {
  $display_title = $order->totals[$i]['title'];

    echo '          <tr>' . "\n" .
         '            <td align="right" class="'. str_replace('_', '-', $order->totals[$i]['class']) . '-Text">' . $display_title . '</td>' . "\n" .
         '            <td align="right" class="'. str_replace('_', '-', $order->totals[$i]['class']) . '-Amount">' . $order->totals[$i]['text'] . '</td>' . "\n" .
         '          </tr>' . "\n";
    $order_total = $order->totals[$i]['text'];
  }

    echo '          <tr>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>Amount Paid:</strong></td>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>' . $currencies->format($so->amount_applied) . '</strong></td>' . "\n" .
         '          </tr>' . "\n";

    echo '          <tr>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>Balance Due:</strong></td>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>' . $currencies->format($so->balance_due) . '</strong></td>' . "\n" .
         '          </tr>' . "\n";
?>

and replace with:

<?php
  for ($i = 0, $n = sizeof($order->totals); $i < $n; $i++) {
  $display_title = $order->totals[$i]['title'];

    echo '          <tr>' . "\n" .
         '            <td align="right" class="'. str_replace('_', '-', $order->totals[$i]['class']) . '-Text">' . $display_title . '</td>' . "\n" .
         '            <td align="right" class="'. str_replace('_', '-', $order->totals[$i]['class']) . '-Amount">' . $order->totals[$i]['text'] . '</td>' . "\n" .
         '          </tr>' . "\n";
    $order_total = $order->totals[$i]['text'];
  }

    echo '          <tr>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>'. ENTRY_AMOUNT_APPLIED.'</strong></td>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>' . $currencies->format($so->amount_applied) . '</strong></td>' . "\n" .
         '          </tr>' . "\n";

    echo '          <tr>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>'. ENTRY_BALANCE_DUE.'</strong></td>' . "\n" .
         '            <td class="dataTableContent" align="right" valign="top"><strong>' . $currencies->format($so->balance_due) . '</strong></td>' . "\n" .
         '          </tr>' . "\n";
?>

In the language file YOUR_ADMIN_FOLDER\includes\languages\YOUR_LANGUAGE\super_invoice.php add two defines

define('ENTRY_AMOUNT_APPLIED', 'Amount Applied:');
define('ENTRY_BALANCE_DUE', 'Balance Due:');