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

Quote:

---

Originally Posted by sanji

I have not upgrade yet from 1.3, as I absolutely need the order editing feature. In the previous version, JeffD released some changes ( http://www.zen-cart.com/forum/showpo...5&postcount=54 ) that allowed to use the order editor, and even to add products to an order.

Is there something available for the 2.0 version? For me, this it really the most important feature I need for my shop, so I will need to stick to 1.3 if it is not possible to do it on 2.0...

---

As I said in a previous post, this feature is extremely complicated and will be a futile effort when the attribute revisions are introduced. Since I am comfortable editing my orders directly via the DB, I don't plan to build this code. I'm not trying to leave you guys in the code, but my time is really restricted, especially for pro bono work. If you are willing to pay, I will have an opening in my freelance schedule at the end of the month. :smile:

Quote:

---

Originally Posted by wickedklown

The first one is, why are my paypal customers shows as a balance due? do i have to manualy add a payment showing that they paid with paypal?

---

Yes, however I have automated that recently while doing some freelance customizations. Expect it in an updated version.

Quote:

---

secondly, when someone uses our merchant, do they also show as balance due?

---

Not sure exactly what you mean, but the only place those payment line items are displayed is in the Admin. If your merchant isn't looking there, they won't see them.

Quote:

---

Originally Posted by Bjorn

I did notice that the 'Point order at a different customer' feature doesn't work. No adjustment is made when opting to move the order to a new customer. Anyone else noted this issue?

---

No it does work, your just expecting it in the wrong place. That edit option only changes the customers_id field attached to the order. It does not change the customer data attached to the order. If you want to change name, address, e-mail etc, you have to do that manually. This goes back to simple user logic: even if the order is attached to the "wrong" account, they obviously supplied the data you've got for a reason. It should not be changed without equally good reason.

Try this, change the customer from the edit screen, then do a search for that customer from Admin > Customers > Customers. When you find that customer, pull up the orders that are attached to them...viola.

Quote:

---

Found a snippet of code pointing to the admin directory for product images on the packing slip.

---

Well it actually does correctly point at the catalog, hence the DIR_WS_CATALOG . DIR_WS_IMAGES. However your syntax is more accurate, and I will update the code.

Quote:

---

Originally Posted by gmoyle

One change that I made. I currently do not have a Fax for my business, so there is no reason for me to have an empty fax on my invoice.

I changed line 89-90 on super_invoice.php to this.
<td class="invoiceHeading" align="left" valign="top"><?php if (STORE_FAX != ''){echo HEADER_FAX;} ?></td>
<td class="invoiceHeading" align="left" valign="top"><?php if (STORE_FAX != ''){echo STORE_FAX;} ?></td>

so that if down the road I add a fax, and fill the info in the admin, that the information will then automatically show on my invoices, but for now, it doesnt.

---

Good call, I've added that logic to the source. You'll see it in the next version.

I am going to ignore the CSS vs. table discussion that this post generated, and ask that you all do the same. If you want to discuss layout, we have a forum for that; stay on topic. :smile:

Quote:

---

Originally Posted by DogTags

In addition to the Invoice Button, Shipping Label Button, and the Packing Slip Button, it would be nice if there were a Receipt Button cuz some orders come in over the phone and some customers like to have a receipt faxed to them.

It would be the same output as the Invoice Button, just that the word Invoice would be changed to the word Receipt

---

You're right, it would be very simple. But a better idea might be to dynamically change the title of the existing invoice to say "Receipt" or "Invoice" based on the balance due. :wink2:

Quote:

---

Originally Posted by madk

Bad news: I'm having 2 small issues.

1. When I print an invoice dirrectly under store information I get a line that says 'Fed Tax ID #FED_TAX_ID_NUMBER'. I realize this is something that should be defined somewhere but I do not see it anywhere. I did have some trouble upgrading my SQL so I possibly missed something.

2. All my new orders show a payment already listed under payment histroy. There is no name/number or type. Amount is listed as $0.00. Date Posed and modifed is listed as 12/31/1969 18:59:59.

---

The two problems together, combined with your honest admission to SQL trouble leads to believe that the SQL file is your problem. Restore from your backup, and run the SQL again. I recommend you run it from within phpMyAdmin, as that will give you useful error messages should a problem arise again.

I do appreciate you openly mentioning the SQL issues; it makes torubleshooting sooooo much easier. :bigups:

Quote:

---

Originally Posted by duncdamonk

To the first question, could I just knock that bit of code out so I don't have it at the top or even the tax column on the invoice?

---

See above. If the field is blank, the files are smart enough to hide it's display.

Quote:

---

Originally Posted by wickedklown

it seems that when i set an order to refund using super orders. the order calculated correctly and all seemed well, however when i went to the catalog to login and check the order as the customer would see it. the order was gone. It wouldnt show at all...

it looked like i had never made the order.

anyone know why this is? or how to fix it?

---

When you say "I set an order to refund," you mean that you created a refund line item? If so, that will have no effect whatsoever on the order appearing for the customer. In fact, none of this code affects what the customer sees (unless, of course, you delete the order).

Quote:

---

Originally Posted by BlindSide

The two problems together, combined with your honest admission to SQL trouble leads to believe that the SQL file is your problem. Restore from your backup, and run the SQL again. I recommend you run it from within phpMyAdmin, as that will give you useful error messages should a problem arise again.

I do appreciate you openly mentioning the SQL issues; it makes torubleshooting sooooo much easier. :bigups:

See above. If the field is blank, the files are smart enough to hide it's display.

---

So you're saying that I should take out the 00-00000 and leave it blank? I'm have the same kind of issue as that guy did with it showing the column instead of the numbers. Also, the tax field is showing "None!".

Quote:

---

Originally Posted by BlindSide

I am going to ignore the CSS vs. table discussion that this post generated, and ask that you all do the same. If you want to discuss layout, we have a forum for that; stay on topic. :smile:

---

I apologize BS. I guess I was having a self richeous moment. Not only off topic, but barely applicable since we're in admin with this mod. I just finished a debate at the university where I work on the merits of accessible web development and I was still in a "mood". Won't happen again.

- Steven

Quote:

---

Originally Posted by duncdamonk

So you're saying that I should take out the 00-00000 and leave it blank? I'm have the same kind of issue as that guy did with it showing the column instead of the numbers. Also, the tax field is showing "None!".

---

Correct. if the field is blank (FED_TAX_ID_NUMBER == ''), then it does not display. This is also the same logic at work in the "None!" for taxes. If your non-profit, you dont charge taxes; so if you have a Tax ID number, it just removes those fields for you automagically. Delete the number in the field entirely.

@s_mack: Don't think another minute on it, I just didn't want the thread to steer off course. It's an important topic, and one that W3 better handle adequately with CSS3 revisions.