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

Nevermind!

The answer is on pages 17-19 of this same thread. Thanks BlindSide!


:thumbsup::thumbsup::thumbsup::thumbsup::thumbsup:

Quote:

---

Originally Posted by MB1

so what does this thing do? i'm running sales report and edit orders (not to happy with edit orders as it doesn't work that great), is this module do this and then some

---

Super Orders is a big add-on to the stock order management pages. Lots of features most full-time businesses need for order fulfillment and accounting purposes. Download a copy and read the readme file for all the details. I wrote the Sales Report as well, so you already know what you're getting. :wink2:

There are no editing features in the current release, but the next one will have them.

Quote:

---

Originally Posted by Stevietheman

I'm sorry if this has already been reported, but on the bottom of the order detail page, the "Add New Status/Comments" textarea is very narrow if I'm using IE6, but if I'm using Firefox 2, it's roughly 350 pixels wide, pretty much the width I expect.

I normally can fix things like this, but this one is escaping me.

Any ideas?

---

Search the thread for an answer to this one. I seem to recall discussing it right around the release of IE7.

Really the best solution is to switch to Firefox, though. :P

First off I am shy about posting in a public forum so I apologize but I need to know something ever so simple, will this MOD run using the override system?

Nevermind I found it, I just didnt go deep enough :oops:

Oh boy now I do feel like a dumbass

LOL, don't worry about it. Take a look at my early post history and you'll find several posts just like that.

I often find that I can solve my problem simply by trying to type out an explanation for the forum. It forces me to step back and clearly define the issue, often leading me to consider a solution I didn't see earlier because I was focused on the problem.

One more stupid question, do I need to manually insert the SQL patch into phpmyadmin?:censored: Hope not, or can I run it from within the admin section of the cart? I know code and stuff like that but MYSQL scares the crud out of me worse than a trip to the dentist

Quote:

---

Originally Posted by BlindSide

Search the thread for an answer to this one. I seem to recall discussing it right around the release of IE7.

Really the best solution is to switch to Firefox, though. :P

---

Thanks for your response.

I am seeing the problem with IE6, and it's a case where I, as an administrator of my client's store, use Firefox (so I'm OK), but my client still uses IE6, and he's the one who will use the admin area to process [super] orders. I haven't been able to get him to switch to Firefox as of yet (it's hard to get some people to see the advantages of using an alternative browser).

I found a discussion in this thread relating to IE7, but I couldn't discern a specific workaround I could implement. Is there one?

Thanks!

Hi All,
Is anyone using QBI? I'm finding that discounts added to an order from the backend do not get recognized by QBI. I am guessing that Super Orders has created an entirely new field rather than use the existing coupon field. Has anybody already figured this out or know what field these discounts are being saved as. (If "field" is not the appropriate term please excuse my ignorance, lol.)

Thanks!
Audra

Quote:

---

Originally Posted by tncproweb

One more stupid question, do I need to manually insert the SQL patch into phpmyadmin?:censored: Hope not, or can I run it from within the admin section of the cart? I know code and stuff like that but MYSQL scares the crud out of me worse than a trip to the dentist

---

The "SQL Query Executor" tool in the Admin should work fine, but I always personally recommend using phpMyAdmin because it's just more robust and secure. It's also equally painless. Log in > select the DB > click the "SQL" tab > Browse to the file in the "Location of the textfile:" box > Click "Go"

Quote:

---

Originally Posted by Stevietheman

Thanks for your response.

I am seeing the problem with IE6, and it's a case where I, as an administrator of my client's store, use Firefox (so I'm OK), but my client still uses IE6, and he's the one who will use the admin area to process [super] orders. I haven't been able to get him to switch to Firefox as of yet (it's hard to get some people to see the advantages of using an alternative browser).

I found a discussion in this thread relating to IE7, but I couldn't discern a specific workaround I could implement. Is there one?

Thanks!

---

The latest version of Zen Cart has the same fix in admin/orders.php. A quick look leads me to think the solution is in the CSS...

Code:

---

textarea {
width: 80%;
}

---

If that's not in your admin stylesheet, put it there and see what happens.

Quote:

---

Originally Posted by audradh

Hi All,
Is anyone using QBI? I'm finding that discounts added to an order from the backend do not get recognized by QBI. I am guessing that Super Orders has created an entirely new field rather than use the existing coupon field. Has anybody already figured this out or know what field these discounts are being saved as. (If "field" is not the appropriate term please excuse my ignorance, lol.)

Thanks!
Audra

---

Do you mean discounts, as in adding a new line to the order total, or are you referring to refunds, the red payment lines? If the former, I would guess that QBI is looking "too specifically" at the order total lines, and thus ignoring the custom ones.

If the latter, all purchase orders, payments, and refunds exist in an independent table structure, and definitely won't show up in QBI without some customization.

Quote:

---

Originally Posted by BlindSide

The latest version of Zen Cart has the same fix in admin/orders.php. A quick look leads me to think the solution is in the CSS...

Code:

---

textarea {
width: 80%;
}

---

If that's not in your admin stylesheet, put it there and see what happens.

---

This CSS setting was already there in the v1.3.7 Zen Cart I had installed/configured. So the problem must have another origin.