DiamondSea

Sorry, I'm trying to keep up, but am plenty busy with my day to day workload to devote a whole lot of time on here... I'm trying.... :-) - Brian

I'd be happy to work on this if someone can point me to a site having this problem, and give me the Parse_Times from running it both with and without STS. - Brian

The changes you make in product_info.php you will also need to make in sts_product_info.php and assign the appropriate information to a template variable. Look at the difference between product_info.php and sts_product_info.php to see how it's done. - Brian

Use the $langid variable in your image path names. ie: /img/logo/banner-$langid.gif Then create banner-1.gif, banner-2.gif, etc, depending on the languages being used. The number for the LangID will come from your particular osC implementation. - Brian

I believe this is an osC problem, not an STS one. Sorry... - Brian

mcseay just pointed out a bug in the STS3beta2 templates: This should fix the problem. This is something that probably everybody will need to fix until the next version goes up. Sorry I missed this one! - Brian

In .../includes/sts_templates/*/sts_osc_javascript.js remove the first and last lines from the file: <script language="javascript"><!-- from the beginning and --></script> from the end. That will prevent the error messages. This will be fixed in the next release. - Brian

New Simple Template System (STS3) v3.00 Beta 2 Available: New: Manufacturer templates (and manufacturer bugfix from old versions) CHANGELOG.txt from v3.00 Beta 1 CHG: Change samples and live code in sts_user_code to use the defined $sts_block_name variable when assigning values to $template[] CHG: Detect and user Manufacturer templates when searching by manufacturer. Uses index.php_mfr.html for the default manufacturer template, or index.php_mfr_##.html (replace ## with manufacturer id) for per-manufacturer templates CHG: Added $templatepath / $templatedir variables for scripting directory location of template files in templates CHG: Modified .../sts_templates/osc/ templates to use $templatepath variables in templates to specify .js and .css files ADD: Created copy of .../sts_templates/osc/ in .../sts_templates/mysite/ for a play area, preserving /osc/ for testing CHG: Modify defaults in configure-SAMPLE.php to use "mysite" template directory CHG: Quick Install summary in README.txt ADD: sts_functions.php file for some extra routines that will be used later

The installation instructions are pretty much the same, except the layout of the template files has changed a bit. Best and easiest way to install: 1) Install Clean MS2.2 version 2) Test and see if it works 3) Go into /catalog/includes (or whatever you called it) 4) Extract all the STS3 files from the ZIP file, preserving the directory structure. 5) Copy the define statements from the end of configure-SAMPLE.php to your working configure.php file 6) Test and see if it works 7) Done. You can then start playing with the templates. I recommend creating/modifying your templates in this order, and one at a time: 1) sts_templates.html This sets the general look and feel for your entire site. This is the only required template. If you want to further customize your site, then you can also create: 2) index.php_0.html This is the template for the home page category 3) index.php_???.html These are the templates for specific categories, where ??? should be replaced by the categoryID or cPath for the category 4) product_info.php.html This is the generic product_info template. 5) product_info.php_c???.html This lets you set a product_info template by category (note the "c" before the "???"). ??? should be replaced by a category id or cPath. 6) product_info.php_???.html This lets you set a product_info template by product id. ??? should be replaced by the product id for the item. 7) index.php_mfr.html (New to the version 3.00b2) Lets you define a generic template for the "Search by Manufacturer" pages. 8) index.php_mfr_???.html (New to the version 3.00b2) This lets you define a manufacturer template by Manufacturer ID. - Brian

The installation instructions are pretty much the same, except the layout of the template files has changed a bit. Best and easiest way to install: 1) Install Clean MS2.2 version 2) Test and see if it works 3) Go into /catalog/includes (or whatever you called it) 4) Extract all the STS3 files from the ZIP file, preserving the directory structure. 5) Copy the define statements from the end of configure-SAMPLE.php to your working configure.php file 6) Test and see if it works 7) Done. You can then start playing with the templates - Brian

1. GZip compression worked when I tried it on my test site. 2. So far, just skipping the scan of the category tables unless $url_* or $urlcat_* are being used. If you can identify specific queries that should be optimized, I'll be happy to look into it more. In fact, that would be particularly useful seeing as other people are having different issues than I am with the sites I'm working on. - Brian

Why did you have to put it outside the sts directory? - Brian

I'd leave the /sts_templates/osc folder alone so you have a known-working reference point for debugging things later. Make a new directory (ie: /sts_templates/yoursite) and change the STS_TEMPLATE_DIR define in your configure.php file to match it. For the easiest debugging, make all files and links root-relative (ie: <img src="/path/to/image.jpg">) with a leading slash and not http:/ at the beginning. This will make the images show correctly when viewing the templates, in your HTML editor, and in both your regular and SSL versions of the pages. Make changes to the sts_template.html file first, which controls the entire site. After you get that working, then work on category or product templates after the basic one is working. If you are using Dreamweaver, you can even use the Dreamweaver templates feature to design your template pages' general design, if you want a handy way of managing all your STS template files. (Sounds confusing, but is pretty easy). - Brian

There should be new template files in /includes/sts_templates/osc/* if you unzipped it correctly. Also, make sure you have all the DEFINEs from the new configure-SAMPLE.php in your configure.php file. Add &sts_debug=1 to your URL in your browser when viewing a page and it will display the template files it is looking for and if it found any of them. That should help track down the error. - Brian

Thanks! Glad it's helpful! If I could just get someone to pay all my bills for me I'd be able to spend a lot more time here! :huh: - Brian