bkellum

The site administrator's didn't take into account that the current method could quickly get out of hand with so many categories/subcategories. It works just fine for a shop with few of each but that is not the case here.
 
I think the best option is to use HTC SEO contribution. This will provide a very easy method for adding descriptions to each category/subcategory/product page within the Admin. It simply adds extra fields to the category/product page creation process that the shop owner can add via the Admin and STS will automatically add it to the $content tag of a single category or product page. This would allow you to get rid of all of the numerous category/subcategory templates and have a single home page template (index.php_0.html) and a single category template (index.php.html) and a single product page template (product_info.php.html).
 
The extra benefits of installing HTC SEO is that is also provides the necessary Search Engine Meta Tags needed for your shop to be found by Google, etc.
 
Highly recommended as it works flawlessly with STSv4.5 and above.
 
Hope this helped you out,

If your shop admin moduels worked BEFORE installing STSv4.6, then look here.
 
What version of osCommerce are you using?
If older than RC2a, then look here.

STS will not work with osCommerce v3.

New STSv4.6 is now Available!!!
 
*Once upload is approved as it is 1MB in size (due to the new sample templates provided).
 
 
Added new Template Folder drop down menu in the admin to easily select all uploaded template sets similar to how Joomla! installs templates.Added new Open Source Template Sets to provide visual examples of the STSv4.6 features and ease of use.
 
Added several new variables in sts_user_code.php.
 
BUG FIXED: The $templatedir$ tag now works properly in all scripts.
 
BUG FIXED: Corrected the code for STS Default enabled to prevent errors (includes/classes/sts.php).
 
BUG FIXED: Corrected method for error messages appearing in the header (Use of $warning_header$ tag)
 
BUG FIXED: Several lines of code modified in the boxes.php file for seamless infobox template implementation.
 
Requires the use of Stop End Characters to facilitate proper variable functions.
 
Built around the idea to separate template sets from dependability of stock osC images and stylesheets.
 
Allows plug and play functionality to easily switch between properly designed template sets. This allows third party template set designers to easily port their designs.
 
STS files are still the same for all osCommerce 2.2 versions
 
Updated all STS documents.
 
Updated Support Thread links.

Take a look here for your solution.
Also, look here before you make any changes.

Keep in mind, the code was and should remained commented out (or removed) if you don't need COMPATIBILITY WITH STS 2 AND 3. These older versions of STS cause your store to run a lot slower than it should and you should avoid the STS2 & STS3 tags that this code creates.
 
STSv4 has it's own banner and footer tags that you should be using in place of the optional tags listed in the sts_user_code.php file.

I am referring to ARAXIS

What you proved is a clean install of 4.6 works on a stock OSC store, it didn't show that upgrading from 4.5.8 to 4.6 as described in the instructions works which is what the problem at hand is.
 
It is one change in one place, not hard to do and I know it was done correctly.

Oh I and I just re-uploaded the 4.5.8 STS folder and removed the code added to admin/modules.php for 4.6 and my site is back working...

STS Module was disabled before the update, I uploaded the STS folder to the correct directories overwriting the previous 4.5.8 files.
 
I then did the following as per your instructions:
 
Find:

switch ($set) {
 
Add After

// START STS 4.1 case 'sts': $module_type = 'sts'; $module_directory = DIR_FS_CATALOG_MODULES . 'sts/'; $module_key = 'MODULE_STS_INSTALLED'; define('HEADING_TITLE', HEADING_TITLE_MODULES_STS); break; // END STS 4.1
 
Find:

eval('$keys .= ' . $value['set_function'] . "'" . $value['value'] . "', '" . $key . "');"); } else {
 
Replace With:

eval('$keys .= ' . $value['set_function'] . "'" . $value['value'] . "', '" . $key . "');"); // STS V4.6 drop start } else { if($key == 'MODULE_STS_TEMPLATE_FOLDER'){ $dir_name = array(); if ($handle = opendir('../'.MODULE_STS_TEMPLATES_FOLDER.'/')) { while (false !== ($file = readdir($handle))) { $pos = strpos($file, "."); if($pos === false){ $dir_name[] = array("id" => $file, "text" => $file); $i++; } } closedir($handle); } $keys .= tep_draw_pull_down_menu('configuration[MODULE_STS_TEMPLATE_FOLDER]', $dir_name, $value['value']); }else{ $keys .= tep_draw_input_field('configuration[' . $key . ']', $value['value']); } } // STS V4.6 drop end
 
Everything was fine before I did this upgrade so something in the code has screwed it up... Running the installation on a stock OSC is not proving anything, install 4.5.8 and then do the upgrade as per your instructions and let me know then.

Hi,
some time ago I posted these errors using FWR´s Error Handling:
 
I found a way to fix it:
Error: Undefined property: sts_default::$enabled
File: includes/classes/sts.php
Line: 94

if ($this->script->enabled==false) {
Change to:

if (isset($this->script->enabled) && $this->script->enabled==false) {
 
Error: Undefined property: sts::$display_debug_output
File: includes/modules/sts_inc/sts_display_output.php
Line: 33

if ($sts->display_debug_output) {
Change to:

if (isset($sts->display_debug_output)) {
 
I hope this will help! :)

Found your error in the instructions, if done as decribed in your instructions the code ends up like below.
 

eval('$keys .= ' . $value['set_function'] . "'" . $value['value'] . "', '" . $key . "');"); // STS V4.6 drop start } else { if($key == 'MODULE_STS_TEMPLATE_FOLDER'){ $dir_name = array(); if ($handle = opendir('../'.MODULE_STS_TEMPLATES_FOLDER.'/')) { while (false !== ($file = readdir($handle))) { $pos = strpos($file, "."); if($pos === false){ $dir_name[] = array("id" => $file, "text" => $file); $i++; } } closedir($handle); } $keys .= tep_draw_pull_down_menu('configuration[MODULE_STS_TEMPLATE_FOLDER]', $dir_name, $value['value']); }else{ $keys .= tep_draw_input_field('configuration[' . $key . ']', $value['value']); } } // STS V4.6 drop end $keys .= tep_draw_input_field('configuration[' . $key . ']', $value['value']); } $keys .= '<br><br>'; } $keys = substr($keys, 0, strrpos($keys, '<br><br>'));
 
This means that the following line is shown twice
 

$keys .= tep_draw_input_field('configuration[' . $key . ']', $value['value']); }
 
Another case of incorrect instructions...
 

New STSv4.6 is now Available!!!
 
*Once upload is approved as it is 1MB in size (due to the new sample templates provided).
 
 
Added new Template Folder drop down menu in the admin to easily select all uploaded template sets similar to how Joomla! installs templates.Added new Open Source Template Sets to provide visual examples of the STSv4.6 features and ease of use.
 
Added several new variables in sts_user_code.php.
 
BUG FIXED: The $templatedir$ tag now works properly in all scripts.
 
BUG FIXED: Corrected the code for STS Default enabled to prevent errors (includes/classes/sts.php).
 
BUG FIXED: Corrected method for error messages appearing in the header (Use of $warning_header$ tag)
 
BUG FIXED: Several lines of code modified in the boxes.php file for seamless infobox template implementation.
 
Requires the use of Stop End Characters to facilitate proper variable functions.
 
Built around the idea to separate template sets from dependability of stock osC images and stylesheets.
 
Allows plug and play functionality to easily switch between properly designed template sets. This allows third party template set designers to easily port their designs.
 
STS files are still the same for all osCommerce 2.2 versions
 
Updated all STS documents.
 
Updated Support Thread links.

I agree. I do not like the new download thought process. Please revert back to the old method. Thank you.

STSv4.6 is just around the corner. I have updated the docs and code and added in the new templates. Now I just need to do some testing and then create the zip package.
 
This version will be quite a bit larger as it includes several sample template sets so I am hoping the Contribution Administrators allow it to be uploaded.
 
 

Check out the following links that will help answer your questions:
 
Important Posts for the STS newbie:
 
Post #3755: http://forums.oscomm...p;#entry1226986
 
Post #4326: http://forums.oscomm...p;#entry1303555
 
Post #4974: http://forums.oscomm...p;#entry1361366
 
Post #3772: http://forums.oscomm...p;#entry1227769
 
Post #3757: http://forums.oscomm...p;#entry1227006
 
Please review the above for insight on how the Simple Template System allows you to make templates for pages, categories, home page, products and infoboxes.
 
Hope this was helpful,

Just one addition to the above, I have a working demo of a default flyout menu using osC RC2a, Dynamenu and STSv4.5.8 at http://www.soundsgoodpro.com/dynamenu2

Try something like this: 
If your one category is category ID=30 (use whatever your cpath=), then create your category template as index.php_30.html. Depending upon your design, you should keep this as lean as possible, meaning you probably only want this to be a single column so it will blend in nicely with your home page template.
 
Now, add the following line of code in your index.php_0.html file (home page template):
 
 

<?php include("index.php_30.html"); ?>
 
Hope this helped,

It appears your designer used "static" links to create your category menu otherwise it would have automatically displayed on the home page. Here is how you create your new static link to your new category:
 
STS Link to a category:
 

<a href="<?php echo tep_href_link('index.php', 'cPath=21&', 'NONSSL'); ?>">Category Name Here</a>
Change the cpath number to the correct category number of your new category.
 
STS Link to a product:

<a href="<?php echo tep_href_link('product_info.php', 'products_id=53&', 'NONSSL'); ?>">Product Name Here</a> Change the product ID number to the product ID number of the product you are linking to.
You can use the links above to create your menus.
Hope this helped,

Bobby,
 
I see that you are new to osCommerce so I can understand your confusion.
 
1. Everything you did so far is correct as far as the template is concerned.
2. Regarding the css menu, you will need to upload the files and folders from the contribution from the catalog folder in the contribution. Keep in mind that the "catalog" represents the root location of where you have osCommerce installed. Really, all you should need is the file that is located in catalog/includes/boxes/categorycss.php (or whatever the filename is as I am just going off memory here). Uplload this file to your catalog/includes/boxes folder. This file is a custom category php script that allows the category menu to be modified using css.
 
3. If you are still having image issues, make sure you have uploaded all of the images from the catalog/images folder from the contribution to your catalog/images file in your shop. Also, make sure you have uploaded all of the images from the catalog/includes/sts_templates/modernrc2a/images in the contribution to your site at the same location.
 
I think the instructions in the add-on could have been more clear but the above should get you where you need to be.
 
Note: STSv4.6 will be out soon and it will make having portable templates sets a lot easier and truly portable from site to site.

Sorry I didn't respond to your request for help. I feel if you don't post in the correct support thread you must not need help all that badly.
 
 

Sorry I didn't respond to your request for help. I feel if you don't post in the correct support thread you must not need help all that badly.
 
 

You need to focus on the installation instructions as you have not installed STS correctly. Suggestion: Use a file comparison tool such as Beyond Compare or WinMerge to compare the files in your shop to the files from the contribution. This will easily show you where you went wrong in the installation and allow you to easily merge in the code to the correct locations in the files.

Ran out of edit time for the above post....
 
 
 
No, v4.5.9 was not a bug fix of anything and since I do not have any control over who can upload to the STS section, it is definitely "Buyer Beware".
Regarding your issue though...it is most likely that you didn't follow the COMPLETE installation instructions (if they are even included with 4.5.9???). You need to upload both the files for RC2 as well as the files in the STS folder.
 
You see, for most contributions, two sets of files are included:
1. Stock osC files that need to be modified
2. And new files that must be uploaded
 
Both sets of files need to be uploaded. Why separate the two? Well, this allows older shop owners an upgrade path by simply uploading the new files and then doing a file compare with the stock files to merge in the changes to thier shop so as not to write over any modifications they have already made. New shop owners can simple upload both sets of files and done with it.
 
STSv4.5.8 by bkellum is the current stable release of the Simple Template System and the only version that I will support.
 
STSv4.6 will be coming within a week (be watching the STS download page).

hejian just posted a "new" version of STS.
 
I see he took out some vital code that makes the infobox templates function correctly. Not a good thing. I also see that he has only posted 2 times in the support forums so good luck getting any support for his so called "fixes".
 
I highly recommend the 4.5.8 release over this one.

Important Posts for the STS newbie:
 
Post #3755: http://forums.oscomm...p;#entry1226986
 
Post #4326: http://forums.oscomm...p;#entry1303555
 
Post #4974: http://forums.oscomm...p;#entry1361366
 
Post #3772: http://forums.oscomm...p;#entry1227769
 
Post #3757: http://forums.oscomm...p;#entry1227006
 
Please review the above for insight on how the Simple Template System allows you to make templates for pages, categories, home page, products and infoboxes.
 
Hope this was helpful,