Zen Cart Logo
Forums / All Other Contributions/Addons / OLD Super Orders 2.0 (See v3.0 thread instead)

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

Locked

Views: 456,074

Results 1,221 to 1,240 of 2,020
This thread is locked. New replies are disabled.
6 Feb 2009, 4:46 AM
#1221
bsteinagel avatar

bsteinagel

Zen Follower

Join Date:
Sep 2007
Location:
Neenah, WI
Posts:
112
Plugin Contributions:
0

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

philip_clarke:

Most likely is that you've forgotten something about how you originally installed super orders. "Normally" you edit orders.php and so you're upgrade has overwritten the modified orders.php, if you re-follow the instructions for installing super orders, everything should work out fine and dandy.

Thanks for your prompt reply Phillip. I did as suggested and I'm still ending up with a fatal error regarding undefined function zen_address_format whenever I press the Details, Shipping Label, Invoice, Packing Slip, or Print buttons. I guess what I'd like to try next is to do a total uninstall of super orders, including the sql patch, and re-install it from scratch. How do I go about uninstalling the sql patch? I modified some of my files as outlined in the readme file, will I have to restore these to their original versions when I uninstall?

I'm not quite sure where the function zen_address_format is being called from. It almost seems as if it's missing in a file somewhere.

Thanks,
Brad

6 Feb 2009, 8:30 AM
#1222
philip_clarke avatar

philip_clarke

Suspended

Join Date:
Sep 2008
Posts:
608
Plugin Contributions:
3

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

Sorry I'm uk based so I've only just got up. The function zen_address_format is in

admin/includes/functions/functions_customers.php
admin/includes/functions/general.php
includes/functions/functions_customers.php

and it's not part of the super orders package, my guess is that a file is not being found, and in all likelihood it needs some php to see what's happening.
Give me an email or PM and we'll go through it.

Philip

6 Feb 2009, 1:34 PM
#1223
nikki72 avatar

nikki72

New Zenner

Join Date:
Dec 2008
Posts:
97
Plugin Contributions:
0

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

thomasw98:

I do not understand this section in the readme:

Outstanding Payments

Location: Admin > Reports > Orders Awaiting Payment

This report displays all your outstanding payment paperwork. Each radio
button will search for orders that are missing the indicated transaction
piece

What is the "indicated transaction piece" for a regular order (i.e. not a PO)? How does the system know that a COD order is missing its payment?

Overall, I am not figuring this out. And when I search for any overdue payments in my system, I always get nothing. :cry:

I am having the same issue. I did a search and couldn't find the answer........ does anyone have an answer ;)

6 Feb 2009, 7:08 PM
#1224
philip_clarke avatar

philip_clarke

Suspended

Join Date:
Sep 2008
Posts:
608
Plugin Contributions:
3

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

nikki72:

I am having the same issue. I did a search and couldn't find the answer........ does anyone have an answer ;)

From a brief look at a test site, the orders appear there if they were COD and then not "closed" using the completed button in green on the bottom right hand of the screen. I had a couple of orders that made it into the Orders awaiting payment section, maybe because I selected COD when filling them in, and when I closed them they disappeared. I would guess that I should use the payment+ button to add a payment detail too really, before closing the order.

Philip.

9 Feb 2009, 2:11 PM
#1225
thieving_gypsy avatar

thieving_gypsy

New Zenner

Join Date:
May 2006
Posts:
87
Plugin Contributions:
0

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

Hello

I ahve a site running Super Orders and I have encountered some problems where the Tax is not displayed in the tax colomn of the Super Invoice even though the product is taxable.

Products Model Tax Unit Price Total
1 x ANT

  • Size: 12 (0111089120) 0111089 None! £11.02 £11.02

The unite price is correct but then the Total column is incorrect as it doesn't add the tax either...

However the Sub-Total value does take into account the TAX and displays correctly...

Can anyone shed any light?

Thanks

Andy

15 Feb 2009, 6:10 PM
#1226
cjeb456 avatar

cjeb456

New Zenner

Join Date:
Feb 2009
Posts:
23
Plugin Contributions:
0

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

Sure this is an easy one for someone!

Does the super_invoice page and the super_orders page look to different places to where heading text is defined?

I will explain why...

I have my super_invoice page showing just how I want now, only showing columns...
PRODUCT
UNIT PRICE
TOTAL PRICE

All works perfect.

I now want the same on the super_orders page. I have amended it so the actual column data works fine - it only shows these 3 columns and the data is correct but the headings are acting strangely

On super_invoice, the last 2 columns headings are...
TABLE_HEADING_PRICE_NO_TAX
TABLE_HEADING_TOTAL_NO_TAX

I entered these column headings onto the super_orders page, but it is just displaying the field name rather than "Unit Price" and "Total" like it does on the invoice

It as though super_orders page cannot find these variables defined whereas super_invoice can.

I am sure I am right that they are looking to different destinations for the definitions, but not sure where.

Pelase could someone help?

Many thanks

15 Feb 2009, 6:16 PM
#1227
cjeb456 avatar

cjeb456

New Zenner

Join Date:
Feb 2009
Posts:
23
Plugin Contributions:
0

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

Found my answer after posting...

super_orders looks to admin/includes/languages/english/super_orders
super_invoice looks to admin/includes/languages/english/super_invoice

Logical really!

The headings I was trying to use were defined in super_invoice but not super_orders

Thanks

16 Feb 2009, 7:33 AM
#1228
tuncay avatar

tuncay

New Zenner

Join Date:
Sep 2006
Posts:
56
Plugin Contributions:
0

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

hi thank you everybody for their help in advance.

philip or anybody, i add super orders and edit orders it seems like evrything go smoothly when i update with edit orders and go back to super orders it seems like balance due isn't updating how can i fix that
and
secondly at the installation of super orders optional file edits #2 is a part about the filenames defines if i change those the edit orders is going to work or not.

thirdly is it possible dit orders can be integrated into the super orders?

16 Feb 2009, 3:26 PM
#1229
danilyn22 avatar

danilyn22

Zen Follower

Join Date:
Dec 2008
Location:
California
Posts:
102
Plugin Contributions:
0

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

I am experiencing the same issues as the post above. I am new to Zen Cart but have had ecommernce sites since 1999. My 2 other sites are hosted ecommerce packages with very robust order pages. When I first saw the stock order page in ZC I knew I needed something more so I loaded Super Orders.

When an order comes in, if I manage it in Super Orders it does not update the Order page that comes installed with Zen Cart so I get confused to where to update orders. If I complete an order in Super Orders it still shows as a new order in Orders.

Can anyone explain how they process their orders.

Also, I prefer to "Authorize only" charges until I ship the order. Is there a way to complete the charge from the admin panel? I do not see this in Super Orders or Orders nor have I found a Mod.
THanks

16 Feb 2009, 9:34 PM
#1230
cjeb456 avatar

cjeb456

New Zenner

Join Date:
Feb 2009
Posts:
23
Plugin Contributions:
0

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

Hi all

Under localization -> Payment Types, I am trying to remove some of the types that I will never use. On the whole this was very straight forward but now I have a problem.

Whilst testing out the features of Super Orders 2.0, I created a few test orders, made test payments and test refunds etc against these orders.

I then went in once I had finished testing them and deleted all these orders.

The problem is, some of the payment types I am trying to delete were used in the payments or refunds on the test orders

It will not let me delete these payments type saying...

Delete Prohibited
This payment type currently has 1 payments and/or refunds attached to it. Those records must first be deleted or moved to another payment type before you can delete this one.

I connot delete the payment, or move it to another payment type because I have deleted the orders that those payments/refunds were against.

How can I make it forget about those payments so I can delete the payment types?

Many thanks in advance

16 Feb 2009, 11:58 PM
#1231
resqjock avatar

resqjock

Zen Follower

Join Date:
Aug 2008
Posts:
114
Plugin Contributions:
0

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

Is there a compatibility issue using "Super Orders" with "Edit Orders"????

Thanks
Stan

17 Feb 2009, 1:27 AM
#1232
resqjock avatar

resqjock

Zen Follower

Join Date:
Aug 2008
Posts:
114
Plugin Contributions:
0

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

I just installed this mod, but I am not able to edit orders, like the instructions claim.

I click on the "edit proucts" link and I get a new page, but there is nothing I can do on this page. it just displays the product.

The instructions state to remove the "orders" link in admin/customer/orders, but if I do tis I will not be able to edit any thing, since I have "edit orders" installed.

Is there something I am missing or doing something wrong, since I can not edit orders in "super orders" ?

Thanks

Stan

17 Feb 2009, 2:35 AM
#1233
tuncay avatar

tuncay

New Zenner

Join Date:
Sep 2006
Posts:
56
Plugin Contributions:
0

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

hi this super orders isn't allowing to edit the products you can divide the order into 2 and for example
a customer order 3 products and you have in stock one of them you can sperate 2 not in stock orders in to new order but you can't add or delete directly from the original order. the edit order addon do that you can add or delete or change anything in the order such as name adress email, product, shipping and tax info. what i write that may be somebody wiser then us combine super orders+edit orders and make it complete. philips clarke is email me that he did that before in one of his test store.

17 Feb 2009, 6:45 PM
#1234
gezuvor avatar

gezuvor

New Zenner

Join Date:
Apr 2007
Location:
Orange County, CA
Posts:
88
Plugin Contributions:
2

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

Hi All,

Great mod, really love it. However, having some issues with our 1.38 installation and the info at a glance feature.

I did a search for this, but didn't see any suggestions to fix it. The bubble is there, but clicking it does nothing... :(

Screen capture from my admin attached, in case I'm missing something...

Thanks in advance, ~Rich

18 Feb 2009, 6:29 PM
#1235
smatric avatar

smatric

New Zenner

Join Date:
Feb 2009
Location:
BC, Canada
Posts:
10
Plugin Contributions:
0

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

Hi all,

I started to cooperate with HiPCTech. We use for our webstore Zen Cart with Super Orders module. We had a problem with "Balance Due". If someone paid through PayPal, Super Orders still showed "Balance Due" to be paid. I've found a solution to this problem and I'd like to post it here so that maybe someone can also find it useful.

Whole changes are made in "zcmanager/includes/classes/super_order.php". I modified "start()" function and added one new ("check_paypal_payments()"). What it does is it basically selects PayPal payments from "TABLE_PAYPAL" where order_id equals "$this->oID" and adds "mc_gross" value to "amount_applied". It takes only payments from "paypalwpp" or "paypal 1.3.8a" or "paypal (ipn-handler)" modules. There might be a better way to do it. Maybe just to select all except for "paypaldp". But for security I wrote it like that.

Here is the code:

  function start() {
    global $db;

    // scrape some useful info from the record in the orders table
    $order_query = $db->Execute("select * from " . TABLE_ORDERS . " where orders_id = '" . $this->oID . "'");
    $this->cID = $order_query->fields['customers_id'];
    $this->order_total = $order_query->fields['order_total'];

    if (zen_not_null($order_query->fields['date_cancelled']) ) {
      $this->status_date = $order_query->fields['date_cancelled'];
      $this->status = "cancelled";
    }
    elseif (zen_not_null($order_query->fields['date_completed']) ) {
      $this->status_date = $order_query->fields['date_completed'];
      $this->status = "completed";
    }
    else {
      $this->status_date = false;
      $this->status = false;
    }

    // build an array to translate the payment_type codes stored in so_payments
    $payment_key_query = $db->Execute("select * from " . TABLE_SO_PAYMENT_TYPES . "
                                       where language_id = '" . $_SESSION['languages_id'] . "'
                                       order by payment_type_full asc");
    while(!$payment_key_query->EOF) {
      // this array is used by the full_type() function
      $this->payment_key_array[$payment_key_query->fields['payment_type_code']] = $payment_key_query->fields['payment_type_full'];

      // and this one can be used to build dropdown menus
      $this->payment_key[] = array('id' => $payment_key_query->fields['payment_type_code'],
                                   'text' => $payment_key_query->fields['payment_type_full']);
      $payment_key_query->MoveNext();
    }

    // get all payments not tied to a purchase order
    $payments_query = $db->Execute("select * from " . TABLE_SO_PAYMENTS . "
                                    where orders_id = '" . $this->oID . "'
                                    and purchase_order_id = 0
                                    order by date_posted asc");

    if (zen_not_null($payments_query->fields['orders_id'])) {
      while (!$payments_query->EOF) {
        $this->payment[] = array('index' => $payments_query->fields['payment_id'],
                                 'number' => $payments_query->fields['payment_number'],
                                 'name' => $payments_query->fields['payment_name'],
                                 'amount' => $payments_query->fields['payment_amount'],
                                 'type' => $payments_query->fields['payment_type'],
                                 'posted' => $payments_query->fields['date_posted'],
                                 'modified' => $payments_query->fields['last_modified']);
        $payments_query->MoveNext();
      }
    }
    else {
      unset($this->payment);
      $this->payment = false;
    }

    // get all the purchase orders for this order
    $purchase_order_query = $db->Execute("select * from " . TABLE_SO_PURCHASE_ORDERS . "
                                          where orders_id = '" . $this->oID . "'
                                          order by date_posted asc");

    if (zen_not_null($purchase_order_query->fields['orders_id'])) {
      while (!$purchase_order_query->EOF) {
        $this->purchase_order[] = array('index' => $purchase_order_query->fields['purchase_order_id'],
                                        'number' => $purchase_order_query->fields['po_number'],
                                        'posted' => $purchase_order_query->fields['date_posted'],
                                        'modified' => $purchase_order_query->fields['last_modified']);

        $purchase_order_query->MoveNext();
      }
    }
    else {
      unset($this->purchase_order);
      $this->purchase_order = false;
    }

    // get any payments that are tied to a purchase order
    if($this->purchase_order) {    // need a po before you can have po payments
      for($i = 0; $i < sizeof($this->purchase_order); $i++) {
        $this_po_id = $this->purchase_order[$i]['index'];

        $po_payments_query = $db->Execute("select * from " . TABLE_SO_PAYMENTS . "
                                          where purchase_order_id = '" . $this_po_id . "'
                                          order by date_posted asc");

        if (zen_not_null($po_payments_query->fields['orders_id'])) {
          while (!$po_payments_query->EOF) {
            $this->po_payment[] = array('index' => $po_payments_query->fields['payment_id'],
                                        'assigned_po' => $this_po_id,
                                        'number' => $po_payments_query->fields['payment_number'],
                                        'name' => $po_payments_query->fields['payment_name'],
                                        'amount' => $po_payments_query->fields['payment_amount'],
                                        'type' => $po_payments_query->fields['payment_type'],
                                        'posted' => $po_payments_query->fields['date_posted'],
                                        'modified' => $po_payments_query->fields['last_modified']);
            $po_payments_query->MoveNext();
          }
        }
      }

      if (sizeof($this->po_payment) < 1) {
        unset($this->po_payment);
        $this->po_payment = false;
      }

    }

    // get any refunds
    if($this->payment || $this->po_payment) {   // gotta have payments in order to refund them
      $refunds_query = $db->Execute("select * from " . TABLE_SO_REFUNDS . "
                                     where orders_id = '" . $this->oID . "'
                                     order by date_posted asc");

      if (zen_not_null($refunds_query->fields['orders_id'])) {
        while (!$refunds_query->EOF) {
          $this->refund[] = array('index' => $refunds_query->fields['refund_id'],
                                  'payment' => $refunds_query->fields['payment_id'],
                                  'number' => $refunds_query->fields['refund_number'],
                                  'name' => $refunds_query->fields['refund_name'],
                                  'amount' => $refunds_query->fields['refund_amount'],
                                  'type' => $refunds_query->fields['refund_type'],
                                  'posted' => $refunds_query->fields['date_posted'],
                                  'modified' => $refunds_query->fields['last_modified']);
          $refunds_query->MoveNext();
        }
      }
      else {
        unset($this->refund);
        $this->refund = false;
      }
    }

    // calculate and store the order total, amount applied, & balance due for the order

    // add individual payments if they exists
    if($this->payment) {
      for($i = 0; $i < sizeof($this->payment); $i++) {
        $this->amount_applied += $this->payment[$i]['amount'];
      }
    }

    // next add the po payments if they exist
    if ($this->po_payment) {
      for($i = 0; $i < sizeof($this->po_payment); $i++) {
        $this->amount_applied += $this->po_payment[$i]['amount'];
      }
    }

    // now check PayPal payments and add if they exist
	$this->check_paypal_payments();
    $this->amount_applied += $this->paypal_total_payments;

    // now subtract out any refunds if they exist
    if($this->refund) {
      for($i = 0; $i < sizeof($this->refund); $i++) {
        $this->amount_applied -= $this->refund[$i]['amount'];
      }
    }

    // subtract from the order total to get the balance due
    $this->balance_due = $this->order_total - $this->amount_applied;

    // compare this balance to the one stored in the orders table, update if necessary
    if ($this->balance_due != $order_query->fields['balance_due']) $this->new_balance();

  }   // END function start

  function check_paypal_payments() {
  	global $db;

  	$this->paypal_total_payments = 0;

  	$paypal_payments_query = $db->Execute("select * from " . TABLE_PAYPAL . "
  											where `order_id` = '" . $this->oID . "'
  											and `payment_status` = 'Completed'
  											and (`module_name` = 'paypalwpp'
  											  or `module_name` = 'paypal 1.3.8a'
  											  or `module_name` = 'paypal (ipn-handler)')");

  	if (zen_not_null($paypal_payments_query->fields['order_id'])) {
		while (!$paypal_payments_query->EOF) {
			$this->paypal_total_payments += $paypal_payments_query->fields['mc_gross'];
			$paypal_payments_query->MoveNext();
        }
  	}
  }
19 Feb 2009, 9:42 PM
#1236
cjeb456 avatar

cjeb456

New Zenner

Join Date:
Feb 2009
Posts:
23
Plugin Contributions:
0

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

cjeb456:

Hi all

Under localization -> Payment Types, I am trying to remove some of the types that I will never use. On the whole this was very straight forward but now I have a problem.

Whilst testing out the features of Super Orders 2.0, I created a few test orders, made test payments and test refunds etc against these orders.

I then went in once I had finished testing them and deleted all these orders.

The problem is, some of the payment types I am trying to delete were used in the payments or refunds on the test orders

It will not let me delete these payments type saying...

Delete Prohibited
This payment type currently has 1 payments and/or refunds attached to it. Those records must first be deleted or moved to another payment type before you can delete this one.

I connot delete the payment, or move it to another payment type because I have deleted the orders that those payments/refunds were against.

How can I make it forget about those payments so I can delete the payment types?

Many thanks in advance

Does anyone have advise on this please?

Thanks

19 Feb 2009, 10:08 PM
#1237
carlvt88 avatar

carlvt88

Zen Follower

Join Date:
Aug 2007
Location:
Williston, Vermont
Posts:
180
Plugin Contributions:
0

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

I don't use this feature of sales orders, so this may not be too precise, but I looked at the code and it looks like it's checking in the TABLE_SO_PAYMENTS and TABLE_SO_REFUNDS to see if those payment types are used.

My guess is that when you deleted the order, you may have done this through the stock Customers->Orders instead of Customers->SuperOrders. If this is the case, the order was removed from TABLE_ORDERS, but still exists in those other tables.

I'd probably manually remove the one record from the TABLE_SO_PAYMENTS table using PhpMyAdmin - assuming that this record is associated with a non-existant order ID anyway.

27 Feb 2009, 6:27 AM
#1238
voltage avatar

voltage

Totally Zenned

Join Date:
Apr 2005
Location:
Houston, TX
Posts:
1,356
Plugin Contributions:
1

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

tuncay:

what i write that may be somebody wiser then us combine super orders+edit orders and make it complete. philips clarke is email me that he did that before in one of his test store.

I just combined the two. I am no programmer but the following worked for me.

Install both mods: edit order and super orders. Make the option filenames update for super orders.

open up filenames.php at includes/filenames.php and add this line:

define('FILENAME_EDIT_ORDERS', 'edit_orders');

Open up admin/super_orders.php and find this line:

echo '<a href="' . zen_href_link(FILENAME_SUPER_DATA_SHEET, 'oID=' . $oID) . '" target="_blank">' . zen_image_button('btn_print.gif', ICON_ORDER_PRINT) . '</a>  ';

Add this line right above it:
echo '<a href="' . zen_href_link(FILENAME_EDIT_ORDERS, 'oID=' . $oID) . '">' . zen_image_button('button_edit.gif', ICON_ORDER_EDIT) . '</a>  ';

27 Feb 2009, 7:41 AM
#1239
philip_clarke avatar

philip_clarke

Suspended

Join Date:
Sep 2008
Posts:
608
Plugin Contributions:
3

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

Sorry I've been off due to repeated illness and this is not "my module" (the original developers disappeared quite sometime back).

The only issues with combining the modules are 1) the orders.php used as a basis for super orders dates back to about 2007 and so sometimes it doesn't work on later versions. 2) super_orders or edit_orders both use window.back() in their links to go backwards through results which can mean repeated clicks through to the wrong places. 3) bad totalling of discounts or order re-totalling.

I'd solved quite a few of the problems certainly 1 and 2, but 3 remained an issue. Until I sorted some of the other issues with my own modules (and got healthier) I'll not be looking at this module's totalling up problems. I agree it was quite easy to just put them up on the same zen-cart shop but over time they don't play nicely together and the totalling and re-totalling appears to move further from the desired or correct values.

Philip.

28 Feb 2009, 5:37 AM
#1240
tuncay avatar

tuncay

New Zenner

Join Date:
Sep 2006
Posts:
56
Plugin Contributions:
0

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

:clap:voltage great thanks a lot i did what you say yes it is working. only not working part is when you edit with edit orders the balance due isn't updating automaticly . however if i go edit order totals (under super orders) click and at the next window click on submit then it updates do you have any fix for that too if you have it is going to be great.

thanks again for the great job :clap: