Looking for visual clues to layout

I've installed Zen-Cart 1.3.8, have found enough info that I think I understand what I need to do to make this look & feel just like my existing website (still a WIP). Thus far, this looks like a great system to work in.

But I am wondering if anyone has come up with a flow chart that shows what is related to what, and how they interact in the initial installed site? Also, is there a listing somewhere of all the files in the install - with some information regarding their functions? It would be useful to have something like that, just to get a better feel for how this thing functions. I know HTML & am learning php, but sometimes it's hard to follow a non-linear system like this, to be sure I've covered everything - and to try to avoid really screwing up by making the wrong assumptions about functionality of the parts of the system.

One more thing, is there a diagram that shows the locations of the various parts that make up the initial page, something like an arrow that points to the main side box and says that's what it is?

Two links to become familiar with are at the top of this page: FAQ and Wiki

If you search the FAQ using 'overrides' you will find some answers to your questions. After that you can always search the Forum itself using whatever keyword, to find threads of others that were having the same problem.

You can find the program flow docs in the add-ons, here:
http://www.zen-cart.com/index.php?main_page=product_contrib_info&cPath=40_54&products_id=378

OK, thanks - both of those help. I got a good night's sleep so thinks look a bit clearer right now...:clap:

A question I don't see (or missed) is if overrides are limited to just the file, or extend to a function. In other words, if I just need some of the functions of the page, do I need to retain all other functions on that page, or can I just have the ones I need and assume the rest of the functions will be loaded from the original page?

There are a lot of functions you can turn on or off using the admin side of your cart. The "e-start Your Web Store with Zen Cart" book is a user's manual for admin features (link on home page).

The override system is for customizing the looks and text of your custom store pages.

These tutorials will help you get started. You will be working with copies of the orginal (core) files. You'll need a good text editor, like notepad++, and an good FTP program (Filezilla is recommended frequently). Download Zen Cart and unzip it on your hard drive to learn ZC's file structure, and to make file copies.

https://www.zen-cart.com/tutorials/index.php?article=143
https://www.zen-cart.com/tutorials/index.php?article=142

Hope this helps!

TShooters:

There are a lot of functions you can turn on or off using the admin side of your cart. The "e-start Your Web Store with Zen Cart" book is a user's manual for admin features (link on home page).

The override system is for customizing the looks and text of your custom store pages.

These tutorials will help you get started. You will be working with copies of the orginal (core) files. You'll need a good text editor, like notepad++, and an good FTP program (Filezilla is recommended frequently). Download Zen Cart and unzip it on your hard drive to learn ZC's file structure, and to make file copies.

https://www.zen-cart.com/tutorials/index.php?article=143
https://www.zen-cart.com/tutorials/index.php?article=142

Hope this helps!

It does, thanks. But in the second link, all you are doing is adding the modified template_info.php to your template...but what I don't see is if I need to use the Admin panel & overrides to do the layout, or if I can bring my old HTML/php into the template to do the things I need to do...and if so, how do I link that code to the overrides? How much do I have to redo of the work I've already got done that really just needs a shopping cart?

Take a look at the existing page - http://www.orcatools.com/OrcaToolsWIP/index.php - which is a real pig code wise (since I was learning from an example that I still don't understand), but is functional up to the point of placing and servicing the order. What I would like is to simply tie in the functions of ZC that do the cart, PayPal & email, and get this beast up & running. Or do I have to learn yet another system - and move all of the code over into ZC in order to do that? I like the ZC system, and if I was starting from scratch it would be a great way to go...but I hope I don't have to start from scratch...again.

And please, don't think I'm ragging on you about this - I really do appreciate the help. But I also need to see some kind of diagram that tells me how this thing works - enough that I can take my own solutions and meld the two in a functioning system. I see bits & pieces, but not a general structure with functionality noted. The override setup makes sense - but how do I get my code to port to it in a rational, and coherent, manner by the end of this weekend? :frusty::lamo:

Again, many thanks for the help...and I may have more questions later...or it may all come clear after a good night's sleep...assuming the cat doesn't play tail tag on my chest at 6 AM...:laugh:

"if overrides are limited to just the file, or extend to a function."

When you do a template override, you use a whole file in the custom folder. But only the customized parts of that file need to be changed. Files do not cover a whole page - often a file will only be responsible for one small box or a function. As a rule of thumb, /includes/modules/ files are responsible for creating the basic information in a page element, and /includes/templates/ files are responsible for massaging that information into the output.

Usually external code (unless it's a plugin that has been designed to be portable) can't just be dropped in, it has to be translated to use the correct variables etc,

gjh42:

"if overrides are limited to just the file, or extend to a function."

When you do a template override, you use a whole file in the custom folder. But only the customized parts of that file need to be changed. Files do not cover a whole page - often a file will only be responsible for one small box or a function. As a rule of thumb, /includes/modules/ files are responsible for creating the basic information in a page element, and /includes/templates/ files are responsible for massaging that information into the output.

Usually external code (unless it's a plugin that has been designed to be portable) can't just be dropped in, it has to be translated to use the correct variables etc,

OK, direct answer - and clears up a number of questions I've considered. I think I am going to clear out my new folders, go back to square one, and give this another try tomorrow morning. With what I've learned today, hopefully it will go better.

:clap:Again, thanks to everyone who helped me work through this.:clap: