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

nagelkruid:

thanks, that is indeed what i was referring to.
funny, i did search the thread and that post didn't come up in my results, and it is even a relative small thread yet....mmmNo worries.. The corrected file will be included in the next release (still working on the updated readme..)

Hi All,

I've just installed the Super Orders Add on (latest one) and it is great.

I've had some sales before hand and now when I go into the super orders screen and click on an order, on the order details screen it is saying that there is No Order Payment Data Available.

I use paypal to process my payments, is there anything I need to do to get these showing up as payment made as it is still showing that the balance is due.

Regards,

Brett Rogers

samar777:

nope. just super orders

DivaVocals:

What version of Zen Cart are you running??

1.3.9.h

samar777:

1.3.9.hDarn.. I was hoping this was a 1.3.8 issue..

Somehow this got missed in the flurry of recent posts..:blush:

lbowenc:

why do the 'Refund Transaction' and 'Void Transaction' functions require me to input values that are either already in the database (last 4 digits) or could be stored in the database with a little effort (trans ID and auth ID)? Why force the user to enter them in order to do a refund or void when they could be saved with the order and retrieved when a refund or void is needed?Not really a Super Orders question since this functionality comes directly from default Zen Cart code. (Remember Super Orders is based on the default orders.php so this is why this behavior is the same for both orders.php and super_orders.php)

I have seen DrByte post the answer to similar questions regarding the notifications.php functionality elsewhere on the forum.. Suggest searching for these posts.. (Try searching the terms 'Refund Transaction' and 'Void Transaction')

lbowenc:

This question could also apply to the base Orders option, but I'm asking here since it could possibly (hopefully) result in an enhancement to Super Orders.
The credit card/PayPal payment notification panel (the grey box which displays this information) comes from default ZEN CART functionality (this same notification panel is displayed on the default orders.php page). This is not specific to Super Orders there is NO INTENT on our part to "fix" this. As a matter of fact we just FIXED the fact that super_orders.php was out of synch with the default orders.php refund/void/auth functionality in v3.0. I have NO PLANS to enhance this ONLY for Super Orders.

IMHO the way to address this is to "fix" the way the notifications.php works so that refunds and voids processed BOTH default in the orders.php and super_orders.php would work the same way. To "fix" this ONLY in Super Orders doesn't make much sense IMHO..

Just upgraded to the latest zencart edition, and then tried to reinstall super orders. Now I can't access the admin page. Can somebody link me to a fix, or what I'm doing wrong?

samuelsmith1979:

Just upgraded to the latest zencart edition, and then tried to reinstall super orders. Now I can't access the admin page. Can somebody link me to a fix, or what I'm doing wrong?
Blank page = error. You need to post the results of the error logs in your store's cache folders..

I have had SO installed and working fine, but I just added Paypal Website Payments Pro along with Express. Now the USPS autofill is not working on orders placed with WPP (cc). It still works fine for orders done thru Paypal express.
It takes me to the USPS site, but none of the customer fields get transfered to the USPS form.
Any ideas?

sailsport1:

I have had SO installed and working fine, but I just added Paypal Website Payments Pro along with Express. Now the USPS autofill is not working on orders placed with WPP (cc). It still works fine for orders done thru Paypal express.
It takes me to the USPS site, but none of the customer fields get transfered to the USPS form.
Any ideas?
You need to ask this on the USPS Autofill module's support thread..

Arrrgh HELP!
SO3 was working great on my live site with test customers.

Just got my first real LIVE order and going into SO I got the following:

1146 Table 'metalpix_db1.TABLE_CUSTOMERS_ADMIN_NOTES' doesn't exist
in:
[select * from TABLE_CUSTOMERS_ADMIN_NOTES where customers_id = '17']
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.

Only thing I have done recently is run the SO3 patch from Fast and easy checkout (I think)

I'm at work so I can't look at the fileset from here.. But all of that admin notes code was removed from SO3. So I'll have to take a look when I get home and see if there is a remnant I'm unaware of in the fileset. Truthfully I don't think there is as I am running SO3 with FEC on my test store and I don't get that error.. (and I'm pretty sure that it's not left in the SO3 fileset) Just out of curiosity, when you say "SO3 patch from Fast and easy checkout", where did you get this patch??

Rizla:

Arrrgh HELP!
SO3 was working great on my live site with test customers.

Just got my first real LIVE order and going into SO I got the following:

1146 Table 'metalpix_db1.TABLE_CUSTOMERS_ADMIN_NOTES' doesn't exist
in:
[select * from TABLE_CUSTOMERS_ADMIN_NOTES where customers_id = '17']
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.

Only thing I have done recently is run the SO3 patch from Fast and easy checkout (I think)

Sent you a PM (I hope)

It was the SO3 part for FEC (explained in the pm)

a2_FEC .... Read it in a post... Not saying that has caused it just letting you know what I've meddled with!

Rizla

It's quietin here ;)

Ok... Would I be safe running SO3 install over my current install?

Indeed that database field does not exist in my setup.

The call for TABLE_CUSTOMERS_ADMIN_NOTES is comming from the admin/super_orders.php that is INCLUDED with the FEC module from the Numinix site.

How should I proceed with this as my PHP is limited???

Was busy last night.. Didn't get your PM until this morning.. I'm at work and I can't look at this here.. but I do have a few observations/suggestions:

The files in the SO3 fileset DO NOT contain ANY references to "TABLE_CUSTOMERS_ADMIN_NOTES" at all.. I'm certain that you are using the super_orders.php file which comes with FEC v1.81. We included instructions in the readme explicitly for users of FEC and COWOA.

Please note this from the SO3 readme:

FEC or COWOA Files
Also included in the fileset are properly modded files to use Super Orders with the Fast and Easy Checkout or Checkout Without Account modules. DO NOT USE the Super Orders files that come with Fast and Easy Checkout or Checkout Without Account. They are for an older version of Super Orders. Super Orders v3.0 already has the correctly integrated Fast and Easy Checkout or Checkout Without Account code in the files includedUsing a file comparison program, you can compare your store's current super_orders.php to the one from the SO3 fileset for FEC if you want to see what I mean. Otherwise I would recommend replacing your super_orders.php file with the one for FEC users from the SO3 fileset.

Rizla:

It's quietin here ;)

Ok... Would I be safe running SO3 install over my current install?

Indeed that database field does not exist in my setup.

Rizla:

Sent you a PM (I hope)

It was the SO3 part for FEC (explained in the pm)

a2_FEC .... Read it in a post... Not saying that has caused it just letting you know what I've meddled with!

Rizla

Rizla:

The call for TABLE_CUSTOMERS_ADMIN_NOTES is comming from the admin/super_orders.php that is INCLUDED with the FEC module from the Numinix site.

How should I proceed with this as my PHP is limited???

I just noticed a "Have a drink" icon to the LHS of the thread title Sticky: Super Orders v3.0 Support Thread (Multi-page thread 1 2 3 4 5 ... Last Page).

I thought this may have meant celebrations were in order for a new release of this module, but I could not find such.

I am still smiling from the Sherry, Shandies and Cointreau had at dinner this evening.

Cheers

I have a client that just gave me the go ahead to upgrade him from 1.3.8a to 1.3.9h. I have super orders installed on his system, but he has not been consistent in using just one (orders vs super orders).

Will this cause any problems for upgrading? Is there anything specific ( sorry, I haven't read the instructions yes :p ) I should be aware of when doing the upgrade?

Really liking what I've read about 3.0 so I'm hoping for a smooth transition.

Thanks!

Deva...
Bang on!!!!
Thanks... Nice to see it back... Cant live without it :)

Thank you

Rizla:

Deva...
Bang on!!!!
Thanks... Nice to see it back... Cant live without it :)

Thank youAll is right with the world again??:smile: (please say yes!!)

chadderuski:

I have a client that just gave me the go ahead to upgrade him from 1.3.8a to 1.3.9h. I have super orders installed on his system, but he has not been consistent in using just one (orders vs super orders).IMHO there is no need to use both. One thing we attempted to do in SO3 was to re-align super_orders.php better with the current orders.php. We even provided EASY integration options for many popular admin mods.. Suggest that if you upgrade you use the files in the "Optional Edits" folder which replace orders.php with super_orders.php.

chadderuski:

Will this cause any problems for upgrading? Is there anything specific ( sorry, I haven't read the instructions yes :p ) I should be aware of when doing the upgrade?

Really liking what I've read about 3.0 so I'm hoping for a smooth transition.

Thanks!You should read the readme IN FULL before you upgrade. It will give you the full scoop on all the changes in SO3 (as does page 1 of this support thread), and the upgrade instructions..:wink: I put a LOT of time and effort into writing that darn readme so that folks would have all the information they needed.. If there is anything that is not clear or covered in the readme, I'll be happy to help clarify those things here, but I don't want to simply re-publish the readme..:smile: