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

Hi I've just installed Super orders and it is a fantastic mod, though I did have trouble with the SQL file and the prefix.

Can anybody tell me how the edit orders functions, I know it has limited functionality at this stage but I just can't see what it does at present.

I read it somehow spilts the orders but after testing this I can't see that it does anything.

Cheers

PS: Thanks Frank for this great mod!

Hi..
I am developing zen cart site. I need to print orders before checkout. I thing Super order do this. Where can i download it?

Dhaya

In regard to the XSS Vulnerability patch for Zen-Cart:

http://www.zen-cart.com/forum/showthread.php?t=64115

Shouldn't the same sort of changes be made in:

super_data_sheet.php
super_edit.php
super_invoice.php
super_orders.php
super_packingslip.php

Not sure if the original author has gone awol or not but. I am in dire need of a fix on SuperOrders,

The e-mail batch update part of SO has never worked for me , and my client is desperate to get it to work.

I have contacted the author by email and PM but so far no reply , if anyone else wants to jump in if they think the can make it work $$$ or £££ waiting ! email me

mark at darksidesolutions dot co dot uk

Regards
Mark

Here is an idea for a future release...

Have the ability to restock products when using the special cancelled button.

Hi there,

Does anyone have any issues with emails at all.
When I try to do a bulk update for orders to notify customer. No email gets sent out. When I look at the order history for those orders I can see a red cross next to notified customer, although the status does update.
If I do a single order at a time, the email works and the green tick is shown on customer notified?

Any Ideas?

Many Thanks

hi all

my store is about selling vegetables and fruits
i m still constructin it ....by hit n trial method:cool:

i want to give u live example what i want to put in my admin:

like i want to know my total sales- product wise on everyday bases like at 21:00 i can get the print out :

list of things purchased on dat very day:
tomatoes 30 Kg
pottatoes 20 Kg
Bananas 10 dozen
& so on...

secondly is there any way i can get the invoice in smaller size and not on full one page:oops:

plz advice how can i get this kidda list on one click:lamo:

Does anyone know how I can do a batch update of orders where "select" is based on product model number, as opposed to payment method, date range, etc.?

Thanks!

All I want to use is the batch order status feature of Super Orders. Do I still need to do all the file mods during installation?

I've noticed there is no option to delete the CVV number for CC payments. This option is available in the standard orders module. Does anyone know another way to do this?

Thanks.

Payment option for Purchase Order not available

Before I paste the sql error in here let me tell you my config.

I am running the following server/zencart config...

** Server Host: **https://www.newvisioncolorlab.com (66.252.131.130) **Database Host: **localhost (127.0.0.1) **Server OS: **Windows NT NVWEB1 5.2 build 3790 **Database: **MySQL 5.0.41-community-nt **Server Date: **07/15/2007 14:46:01 **Database Date: **07/15/2007 14:46:01
**Server Up Time: **
**PHP Version: **5.2.2 (Zend: 2.2.0)
**HTTP Server: **Apache/2.2.4 (Win32) DAV/2 mod_ssl/2.2.4 OpenSSL/0.9.8e mod_autoindex_color PHP/5.2.2 mod_perl/2.0.3 Perl/v5.8.8

After I run the sql update through ZC Admin using the upload method I get the following message when it is done...

1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'True', 'False'), ')' at line 1
in:
[INSERT INTO zen_configuration VALUES (NULL, 'Enable Purchase Order Module', 'MODULE_PAYMENT_PURCHASE_ORDER_STATUS', 'True', 'Do you want to accept Purchase Order payments?', 6, 1, now(), now(), NULL, 'zen_cfg_select_option(array('True', 'False'), ');]
If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.

Just to let you know, i deleted my DB, reinstalled the BU, and then this time, instead of using the upload method in Admin, I just pasted in your SQL text and now this is my result...

**Query Results:**ALTER TABLE zen_orders ADD date_completed datetime default NULL;
ALTER TABLE zen_orders ADD date_cancelled datetime default NULL;
ALTER TABLE zen_orders ADD balance_due decimal(14,2) default NULL;
CREATE TABLE zen_customers_admin_notes ( admin_notes_id int(12) NOT NULL auto_increment, customers_id int(11) NOT NULL default '0', date_added datetime NOT NULL default '0000-00-00 00:00:00', admin_id int(11) NOT NULL default '0', admin_notes text NOT NULL, rating tinyint(1) NOT NULL default '0', PRIMARY KEY (admin_notes_id), KEY customers_id (customers_id) ) TYPE=MyISAM ;
CREATE TABLE zen_so_payments ( payment_id int(11) NOT NULL auto_increment, orders_id int(11) NOT NULL default '0', payment_number varchar(32) NOT NULL default '', payment_name varchar(40) NOT NULL default '', payment_amount decimal(14,2) NOT NULL default '0.00', payment_type varchar(20) NOT NULL default '', date_posted datetime NOT NULL default '0000-00-00 00:00:00', last_modified datetime NOT NULL default '0000-00-00 00:00:00', purchase_order_id int(11) NOT NULL default '0', PRIMARY KEY (payment_id) ) TYPE=MyISAM ;
CREATE TABLE zen_so_payment_types ( payment_type_id int(11) NOT NULL auto_increment, language_id int(11) NOT NULL default '1', payment_type_code varchar(4) NOT NULL default '', payment_type_full varchar(20) NOT NULL default '', PRIMARY KEY (payment_type_id), UNIQUE KEY type_code (payment_type_code), KEY type_code_2 (payment_type_code) ) TYPE=MyISAM;
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'CA', 'Cash');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'CK', 'Check');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'MO', 'Money Order');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'ADJ', 'Adjustment');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'CC', 'Credit Card');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'MC', 'Master Card');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'VISA', 'Visa');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'AMEX', 'American Express');
INSERT INTO zen_so_payment_types VALUES (NULL, 1, 'DISC', 'Discover');
CREATE TABLE zen_so_purchase_orders ( purchase_order_id int(11) NOT NULL auto_increment, orders_id int(11) NOT NULL default '0', po_number varchar(32) default NULL, date_posted datetime NOT NULL default '0000-00-00 00:00:00', last_modified datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (purchase_order_id) ) TYPE=MyISAM ;
CREATE TABLE zen_so_refunds ( refund_id int(11) NOT NULL auto_increment, payment_id int(11) NOT NULL default '0', orders_id int(11) NOT NULL default '0', refund_number varchar(32) NOT NULL default '', refund_name varchar(40) NOT NULL default '', refund_amount decimal(14,2) NOT NULL default '0.00', refund_type varchar(4) NOT NULL default 'CK', date_posted datetime NOT NULL default '0000-00-00 00:00:00', last_modified datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (refund_id), KEY refund_id (refund_id) ) TYPE=MyISAM ;
INSERT INTO zen_configuration VALUES ('', 'Store Fax', 'STORE_FAX', '', 'Enter the fax number for your store.
You can call upon this by using the define STORE_FAX.', 1, 4, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES ('', 'Store Phone', 'STORE_PHONE', '', 'Enter the phone number for your store.
You can call upon this by using the define STORE_PHONE.', 1, 4, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Enable Purchase Order Module', 'MODULE_PAYMENT_PURCHASE_ORDER_STATUS', 'True', 'Do you want to accept Purchase Order payments?', 6, 1, now(), now(), NULL, 'zen_cfg_select_option(array('True', 'False'), ');
INSERT INTO zen_configuration VALUES (NULL, 'Make payable to:', 'MODULE_PAYMENT_PURCHASE_ORDER_PAYTO', 'Destination ImagiNation, Inc.', 'Who should payments be made payable to?', 6, 2, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Sort order of display.', 'MODULE_PAYMENT_PURCHASE_ORDER_SORT_ORDER', '0', 'Sort order of display. Lowest is displayed first.', 6, 4, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Payment Zone', 'MODULE_PAYMENT_PURCHASE_ORDER_ZONE', '0', 'If a zone is selected, only enable this payment method for that zone.', 6, 5, now(), now(), 'zen_get_zone_class_title', 'zen_cfg_pull_down_zone_classes(');
INSERT INTO zen_configuration VALUES (NULL, 'Set Order Status', 'MODULE_PAYMENT_PURCHASE_ORDER_ORDER_STATUS_ID', '2', 'Set the status of orders made with this payment module to this value', 6, 6, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');
INSERT INTO zen_configuration_group VALUES (28, 'Super Orders', 'Settings for Super Order features', 100, 1);
INSERT INTO zen_configuration VALUES (NULL, 'Auto Status - Purchase Order', 'AUTO_STATUS_PO', '2', 'Number of the status assigned to an order when a purchase order is added to the payment data.', 28, 11, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');
INSERT INTO zen_configuration VALUES (NULL, 'Auto Status - Payment', 'AUTO_STATUS_PAYMENT', '2', 'Number of the order status assigned when a payment (not attached to a purchase order) is added to the payment data.', 28, 10, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');
INSERT INTO zen_configuration VALUES (NULL, 'Auto Status - P.O. Payment', 'AUTO_STATUS_PO_PAYMENT', '2', 'Number of the order status assigned when a payment attached to a purchase order is added to the payment data.', 28, 10, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');
INSERT INTO zen_configuration VALUES (NULL, 'Auto Status - Refund', 'AUTO_STATUS_REFUND', '2', 'Number of the order status assigned when a refund is added to the payment data.', 28, 13, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');
INSERT INTO zen_configuration VALUES (NULL, 'Auto Comments - Payment', 'AUTO_COMMENTS_PAYMENT', 'Payment received in our office. Payment ID: %s', 'You''ll have the option of adding these pre-configured comments to an order when a payment is entered. You can attach the payment number to the comments by typing %s.', 28, 14, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Auto Comments - P.O. Payment', 'AUTO_COMMENTS_PO_PAYMENT', 'Payment on purchase order received in our office. Payment ID: %s', 'You will have the option of adding these pre-configured comments to an order when a purchase order payment is entered. You can attach the payment number to the comments by typing %s.', 28, 14, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Auto Comments - Purchase Order', 'AUTO_COMMENTS_PO', 'Purchase Order #%s received in our office', 'You will have the option of adding these pre-configured comments to an order when a purchase order is entered. You can attach the payment number to the comments by typing %s.', 28, 15, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Auto Comments - Refund', 'AUTO_COMMENTS_REFUND', 'Refund #%s has been issued from our office.', 'You will have the option of adding these pre-configured comments to an order when a refund is entered. You can attach the refund number to the comments by typing %s.', 28, 17, now(), now(), NULL, NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Federal Tax Exempt Number', 'FED_TAX_ID_NUMBER', '00-000000', 'If your tax exempt, then you should have a federal tax ID number. Enter the number here and the tax columns will not appear on the invoice. The number will also be displayed at the top of the invoice.', 28, 50, now(), now(), NULL , NULL);
INSERT INTO zen_configuration VALUES (NULL, 'Closed Status - "Cancelled"', 'STATUS_ORDER_CANCELLED', '0', 'Insert the order status ID # you would like to assign to an order when you press the special "Cancelled!" button on super_orders.php.
If you do not have a "cancel" status, or do not want assign one automatically, choose default and this option will be ignored.
You cannot attach comments or notify the customer using this option.', 28, 30, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');
INSERT INTO zen_configuration VALUES (NULL, 'Closed Status - "Completed"', 'STATUS_ORDER_COMPLETED', '0', 'Insert the order status ID # you would like to assign to an order when you press the special "Completed!" button on super_orders.php.
If you do not have a "complete" status, or do not want assign one automatically, choose default and this option will be ignored.
You cannot attach comments or notify the customer using this option.', 28, 30, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');
INSERT INTO zen_configuration VALUES (NULL, 'Closed Status - "Reopened"', 'STATUS_ORDER_REOPEN', '0', 'Insert the order status ID # you would like to assign to an order when you undo the cancelled/completed status of an order. If you do not have a "reopened" status, or do not want assign one automatically, choose default and this option will be ignored. You cannot attach comments or notify the customer using this option.', 28, 30, now(), now(), 'zen_get_order_status_name', 'zen_cfg_pull_down_order_statuses(');

I'm just installing the CC payment module after using an older version of SO with Edit Orders. When I try to complete a test order, I get:

1146 Table 'db.TABLE_SO_PAYMENT_TYPES' doesn't exist
in:
[select * from TABLE_SO_PAYMENT_TYPES where language_id = '1' order by payment_type_full asc]

I'm not a programmer, but this may be because of the SO install? Has anyone else run into this? If I look at SO_PAYMENT_TYPES and it us there and credit cards are listed there. any suggestions? :huh:

Any news on these questions about payments not showing up from PayPal or if you can update them manually? Please see #601.
Thank you!
:frusty:

I thought this mod was working great until I realized that my customers are not receiving any emails now. I have two cart on the same server one with this mod and the other without, the one without the mod works and the one with the mod doesn't. My customers don't receive any order confirmations or updates. Any help!

I'm having same problem. When I check the email archive, it shows the emails were sent, but with no "To:" address (just empty brackets). Since we're still in testing mode, no biggie, but we sure do need to get this working.

Thanks

Anyone experience the prices change in the admin under super orders?

Example, $4.99 item shows up as $172.00 lol

I cant figure this thing out why it does that, any help be appreciated.

This is when a order is made it is correct on the customer side but changed on the admin

jmacdoug:

Just to let you know, i deleted my DB, reinstalled the BU, and then this time, instead of using the upload method in Admin, I just pasted in your SQL text and now this is my result...

Me too. Browse->Upload of the super_orders_sql.sql file via "Admin->Tools->Install SQL Patches" gave me the same error you quoted further above, but when I pasted in the text from the file (again in "Admin->Tools->Install SQL Patches") and applied it via the send button, it worked just fine.

This was with Zen 1.3.7, Database Patch Level 1.3.7, MySQL 5.0.33, PHP 4.4.5, Apache 2.2.4.

wickedklown:

This problem didnt have to do with batch status. it was just when doing order status via super orders. I rarly use batch status update, or any of those batch's.

should i still preform this fix, and will it fix my current problem?

See wickedklown's post of 14th October 2006, 05:24 PM for background.

This was regarding non-scrubbing of <br /> s from status comments added with super orders. I was experiencing the same problem. When adding one status comment to a single order with super orders, my newlines were being stored as <br /> in the database, and the tags would then also appear when the customer viewed the status comment from within the order page in their zencart account. The html email sent to the customer looked as expected: line breaks where there were line breaks in the original text... it was just subsequent re-display of the stored comment on the customer's order page that had the <br /> tags shown.

SO... I discovered a workaround. I "un-supered" the line that super_orders.php uses to scrub the comments and changed it back to the version in plain-old orders.php. In catalog/admin/super_orders.php , in the vicinity of line 100, I made the following change:

//        070722: Changed this line to use same function orders.php uses, to fix improper
//                scrubbing of <br /> from comments.
        $comments = zen_db_prepare_input($_POST['comments']);
//        070722: Original Line
//        $comments = zen_db_scrub_in($_POST['comments']);
```I believe zen_db_prepare_input() is the function that is builtin to zencart to scrub input prior to database storage, and zen_db_scrub_in() is a function from super orders that performs the same task.

Anyhow, a big disclaimer:  This fixed the problem I described, but there obviously is some reason a new function was created to scrub input for super orders, so... user beware.  This may have some undesirable effect that I simply haven't noticed yet, although the fact that orders.php uses this line makes me suspect that this will work OK in most situations.   Time will tell.

Background info: I did this on an installation with: Zen 1.3.7, Database Patch Level 1.3.7, MySQL 5.0.33, PHP 4.4.5, Apache 2.2.4.

OK, regarding my post of 22nd July 2007, 04:29 AM:

There are, in fact, secondary effects from making the mod I outlined. They can be fixed up, I believe, with two edits to super_edit.php and one change to super_orders_functions.php . The end result is that newlines are stored in the database and not <br /> (which is what I wanted), and newlines are converted to <br /> when needed for html output to email, etc. It also fixes the behavior I kept seeing where, after editing status comments with super orders (for one order at a time, not batch mode), <br /> , \n , \r , (or some combination thereof) appearing in status comments would be re-saved to the database as "nr" at the beginning of each line.

So it appears to function the way I want now, with newlines appearing visually as line breaks in all contexts.

However, I can't really recommend it.

One reason is that I am not certain that protection from injection hazards is as good after this mod. It might be, but I'm not an expert in such matters. It isn't a consideration for our situation, as this all runs in the admin side and our admins are limited, non-malicious, and just use it to paste in simple, but multi-line, text. For general use it might be more of a concern.

One other reason I can't recommend it is that I suspect that the intent in altering the scrubbing strategy/code/functions in super orders was to preserve <br /> and other html tags in the database and display them properly in HTML contexts. For some reason there were a few cases in the unaltered code for super orders where status comments would appear with <br /> and also where, after editing status comments, line breaks such as \r\n would be converted, saved and subsequently displayed as "rn" (perhaps the reverse order, "nr", I forget which). These are probably just minor bugs, or it could also be that I, wickedklown, and the other person (somewhere in this thread) who observed "rn"s or "nr"s are doing something when entering or editing status comments that should be done differently to prevent these problems.

My point is that when/if a new rev of super orders is released, I would be willing to bet that the <br /> , \r\n , rn , nr strangeness in status comments will probably be eliminated.

Finally, I haven't tested other HTML tags in the comments, such as hrefs, etc. and can't vouch for how they are handled after modifying superorders as I did. We just need regular text with linebreaks, so it does what we want.

If someone else is having problems with newlines, <br /> , etc. in status comments, I can post the additional mods. PM me if you want the other mods and I'll post them with a big warning.