Quote:
catalog/includes/application_top.php
catalog/includes/classes/shopping_cart.php
catalog/includes/languages/english/product_info.php
Should all be able to have the content from the new contribuiton added directly to them. While they are NOT unchanged, these files have not been split.
From there, it gets tedious. Very worthwhile end results, but tedious.
Quote:
catalog/index.php
is split into 4 modules. The file of the same name sets things up for
Quote:
/catalog/templates/content/index_default.tpl.php
/catalog/templates/content/index_nested.tpl.php
and
/catalog/templages/content/index_products.tpl.php
Each of which does processing under different circumstances. index_default.tpl.php basicly (and I know Tom or Sheetal or someone will correct and expand on this) generates the default mainpage display - at the top level where you have no place higher to go. Index_nested.tpl.php generates the display when you're in the middle of the category tree (ie not at the top, not at the bottom most category, but anywhere in the middle) Index_products.tpl.php generates product displays at the bottom of the category tree where you should have nothing but products.
The advantage is - all the files are smaller, you only load what you need so the site runs more quickly and if you want to make a change at a particular place, you only risk breaking the code in that file - with less code to sort through to find your problem.
The difficulty is in learning what went where, and how to modify it - which is something I hope to address in the Advanced Template System design. (We're a ways out there on that yet, but planning).
Quote:
/catalog/product_info.php
is a bit simpler - it consists of the original file and /catalog/templates/content/product_info.tpl.php[/quote]
By and large, on this file (and most other BTS files) - the *.tpl.php file holds the code usually found near the bottom of the original file - code that generates the actual display. The *.php file will hold sql queries and code that does the actual work of the contribution.
Quote:
/catalog/stylesheet.css
This file is still a bit tricky to decide where to change, but much less so than the others.
Each template file has its own stylesheet.css - located in /catalog/templates/<template_name>. One of the simpler parts of BTS in modifiying catalog side contributions you simply add the new CSS to the stylesheet in each template you plan to use - changing colors and other CSS driven features as needed to make the look and feel match.
Now, I think we have pretty much outlined WHERE to change at least to the file level. Next message should go into a few things INSIDE the files that you will need to look for.
David