Order Invoice - Product Description

[kobra]

You would have to custom code the admin code for this and this is legacy code and table based, noot overrides in ther admin area either so insure that you maintain good notes and copies so as not to loose it on a reinstall for any reason.

[Failed_Attempt]

You would have to custom code the admin code for this and this is legacy code and table based, noot overrides in ther admin area either so insure that you maintain good notes and copies so as not to loose it on a reinstall for any reason.

That just seems odd to me that the product discription would not be included in the invoice....So in other words Im going to have to take my discription with the photo number and edit every product and input that number for the model number per say?

[kobra]

That just seems odd to me that the product discription would not be included

This is because it is an item you want...
Zen Cart can not be one size fits all...although it does try

[jdw1979]

You would have to custom code the admin code for this and this is legacy code and table based, noot overrides in ther admin area either so insure that you maintain good notes and copies so as not to loose it on a reinstall for any reason.

Any hints on what this custom code might be? Or how I could figure it out? Definitely not a PHP developer here...

Pretty please?

[kobra]

Any hints on what this custom code might be? Or how I could figure it out? Definitely not a PHP developer here...

There is a commercial help area on this forum you can post in

[jdw1979]

Well, I must admit that I'm always trying to figure this stuff out for myself, so I can be a better admin of the store. Not to mention, it's cheaper that way.

So...

It seems (after researching the forum) that I need to edit both admin/includes/classes/order.php , and admin/orders.php, right?

I see how the data is inserted and output via the order.php class, which has also helped me discover why the description can't be easily output in the admin interface. There is no products_description field in the orders table! Ah ha! The plot thickens...

So, in order to get the description output in the admin orders interface I have to call the products_description table...which is where I get fuzzy...correlating the correct products_description, in relation to the product_id, and then tie those to their respective oID. Okay...now it's getting to be a lot like math. Damnit.

Little help from the Zen Gurus? I'd love to learn how to do this.

[Ajeh]

First, do you need to know the Product Description forever? Or for as long a the Product is in your database?

What this question means is, if the products_id for the Browns Around Town photo is 33 today, will it always be products_id 33 tomorrow? next week? next year?

And if the Product using products_id 33 got deleted, and next week or next month or next year you look at the invoice ... do you need the description?

If you want a permanent record of the Product Description, then you want to store Today's products_description in the orders_products table to save it forever ...

If you want it as long as it is in the products table and don't care if when you delete the Product you cannot see the Product description and it just reading NOT FOUND vs Today's products_description then you can just use a quick look up ...

So, the question is ... do you need a Today's Products Description or do you want a Forever Products Description on the Order?

[jdw1979]

If you want it as long as it is in the products table and don't care if when you delete the Product you cannot see the Product description and it just reading NOT FOUND vs Today's products_description then you can just use a quick look up ...

This one, totally.

We keep records of all orders in a separate inventory and accounting system (as only a small percentage of our orders come from our website). The thing that my coworkers are unhappy with is that our data feed (over which I have no control...damnit) has stupid, non-descript titles like "Cholestech Accessories" (this title is the same for at least 70 different products). I know, I know, it's clunky and awful. I would just fix the data feed myself, but it's too large to work with manually (60,000 products in our store). Sorry...that turned out to be more like whining than I intended. Thanks a lot for your response.

[Ajeh]

You still need to explain if you need the products_description to be available even if the Product is deleted later after the Orders have been processed etc. of if you just need the Products Description to always be on the Order for each Product ...

If you need it always with the Order, then it will need to be saved in the orders_products table and some numerous code changes are needed ...

If you need it for a short period of time, such as when the Product might be deleted and it is no longer available, you can just use a function to pull the information for display and if the Product is not found then display:
Description Not Found

Which way do you really need this to work?