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

**DivaVocals** · 3 Mar 2011, 05:13 PM

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??

Originally Posted by 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)

**Rizla** · 3 Mar 2011, 07:55 PM

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** · 4 Mar 2011, 08:25 AM

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** · 4 Mar 2011, 03:58 PM

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???

**DivaVocals** · 4 Mar 2011, 05:01 PM

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 included

Using 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.

Originally Posted by 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.

Originally Posted by 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

Originally Posted by 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???

**dw08gm** · 4 Mar 2011, 05:05 PM

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

**chadderuski** · 4 Mar 2011, 07:02 PM

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

) 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!

**Rizla** · 4 Mar 2011, 08:19 PM

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

Thank you

**DivaVocals** · 4 Mar 2011, 10:20 PM

Originally Posted by Rizla

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

Thank you

All is right with the world again??

(please say yes!!)

**DivaVocals** · 4 Mar 2011, 10:28 PM

Originally Posted by 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.

Originally Posted by chadderuski

Will this cause any problems for upgrading? Is there anything specific ( sorry, I haven't read the instructions yes

) 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..

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..