Adding New Product_types

Any clue on how to get the HTML editor up and running with a new product type?

Thanks

I want to add a scheduling system to Zen Cart so that people can schedule appointments for services and pay for them. Where are the appropriate places to start adding the commands that would interact with the database on checkout, when payment has been received, etc.? Is this related to product types at all? The more I think about it, the more I'm thinking I probably just have to edit the pages involved in the checkout process, and add attributes to all of the products I want to be able to schedule to allow for user input on the dates and times they want, or something like that.

Any guidance would be appreciated.

Thanks,

Greg
---
http://www.gregwestin.com

:rolleyes: I have just written a new product type and would like to post it, but i dont know how? can you help. :rolleyes:

A link for a demonstration? You can upload a .zip to your webspace or send the .zip to me at kim @ zen-cart.com

Hi all you great thinkers!
I want to add a new prouct type called accessories, I do not want these products to show in my catalog, I only want to use this new product type in conjuction with the cross sell contribution, so that the only way a customer can purchase this item is as an add on. i.e. If they purchase a dress, they have an option of selecting matching hose.. 2-3 types...
Any suggestions on where to start to do this????

Thanks,
Figster

Hmm, not sure how this would be done as a separate product and product type, but one way to do it (which might be easier overall) is just to use attributes on the original product (e.g., the dress). On the dress product page, have options for the hose (e.g., type1, type2, type3, or none). The appropriate price will be tacked on (you can configure this all in the admin), and it is a sure way to require purchase of the dress to get the hose. The only downside might be that the hose will not have their own inventory tracking or SKUs (they wouldn't appear as a separate item on the order, but just an option under the dress).

In my quest to learn the subject of adding new product types, I've created a duplicate of Product - General. Essentially I have copied and renamed the various files (for both admin & catalog). So all the files for my new product type are copies of those for Product - General with a unique name for respective directories, files, handler.

Everything seems to work fine except my 'Edit Layout' settings for the new product type. This is still being controlled by Product - General settings on the front-end catalog. I've spent quite a bit of time trying to track down the link to the product_type_layout table without success. Could someone point me in the right direction please?

Product type seams to mean a new layout of the product information. I.e. isolate it from the general layout. This is useful if you want: say big picture at the top of you product info page and also the attributes to show in a different style, etc.

I have already sorted all that and in a few days I will give a link to who is interested some options.

In the meantime I would like to known how to get a variable from the tpl_prducts_????????_info_display.php to the cart so I can get the variable onto the order form.

Thanks Peter

PS
Don’t forget you need to upload a SQL file to the database for your product type to work!
PPS
You need to upload all that is in the general products, if you want all the attributes content and bits.

Excuse me please

Get & Post please explain?

The PHP & HTML manuals give little or no explanation as if it is nothing, but it seems to be a big thing?

Please expand I am learning.


Regards

Peter

I'm no expert, but here's the best explanation I have.

GET and POST are both methods of passing information from one page (usually a form) to another. They differ in how they do it.

GET does it by including the information in the URL itself. When you see URLS with "?" and "&" in them, those are usually GET variables being passed.

POST does it in a less visible way, by somehow including them in the actual HTTP request or something. They get sent "under the radar" and are invisible to the user (at least, they are not in the URL). Because of this, POST is usually preferred since it's a little more private/secure.