|Home | Services | JOIN NOW! | About Us | Contact Us | merchant login|
Frequently Asked Questions (FAQ)
Here are some of the most frequently asked questions about STS.
Answer:You need to be using the Milestone 2.2 release of STS. STS does not work "out of the box" with the CVS release due to changes that have been made in the /catalog/include/ files in the CVS release. However, you should be able to do the Advanced Install and get it to work by adding the STS capture codes yourself to the CVS files.
Answer: This has been fixed as of STS version 1.9. Please upgrade to the latest version of STS to take advantage of this fix and other new features that are added regularly.
Answer: You need to upgrade your server's version of PHP. This was a subtle bug in older versions. Updating your PHP will fix it. You should upgrade it anyway, since if you are running a version with this problem, there are also security fixes that have been added to later versions of PHP that you need to secure your system.
Answer: Not "out of the box", but some people have hacked SEC a bit to get them to work together with STS 1.8.
(Check in the forums, as the link that was originally up here is no longer valid)
Answer: Not yet. It is a common request, and I'll work
on it as soon as I can get some time.
Answer: You did not copy the define statements at the bottom of your configure-SAMPLE.php file into your production configure.php file in your /catalog/includes/ directory.
Answer: STS does not control how the boxes look. STS only controls where the boxes appear (or don't appear) on your page. To change the look of the boxes, you'll need to change the code that creates them. Do a search on the forums.oscommerce.com for boxes and you'll find plenty of threads and addons that will help you make the changes you desire.
Answer: The $content variable is filled by capturing the output of the various OSCommerce programs. STS does not control anything about how OSC makes the pages, it only captures the output and lets you layout your site's look-and-feel easily. You would make changes to the $content variable the same way you would make changes to the default install of OSC.
Answer: BTS and STS do two completely different things.
Short Version: BTS for programmers, STS for designers.
BTS doesn't really change the OSC code, but it moves all the display code into separate files from the "logic" code to make it easier for a programmer to modify HOW OSC displays things. BTS is great if you want to modify OSC functionality yourself, but it can also make it difficult to add on contributions afterwards because the code you would normally just compare when adding the contribution's changes has now been split into two different files, the "logic" files and the "display" files.
STS makes a some small changes to the application_top.php, application_bottom.php and column_left.php and column_right.php scripts to capture their output, which then allows STS to map that output into $variables that you can place on your HTML template page.
You can't change WHAT OSC displays with STS, but you can control WHERE it displays it, and put a simple "wrapper" around your $content area to make it look the way you want to.
Bottom line: They're both great packages, but have different uses.
Answer: Depends on the type of code.
You can not put any server-side executable code in STS Template files. STS Template files are treated as a simple text file by STS and no executable codes in it are processed by the STS engine.
Any PHP code in a template file will be sent to the browser un-executed in the HTML source code.
Read STS FAQ # 11: How does STS Work for more of an explanation of why it does this.
If you want to include new features to your code, you will need to create new template variables in sts_display_output.php, sts_product_info.php or sts_user_code.php. You can then put your new template variables wherever you like in the template file(s).
Answer: STS works by selectively capturing the output of the various OSC programs and storing key portions of the output in $template["variablename"] variables. It does this through the STS_START_CAPTURE, STS_STOP_CAPTURE and STS_RESTART_CAPTURE functions.
After all the OSC output has been captured, STS reads in the appropriate HTML Template file into memory. It then performs a find-and-replace for each of the $template variables and then sends the updated file to the client's web browser.
Answer: Make sure that all no url's referenced in your template pages start with HTTP:// (ie: http://me.com/catalog/images/blah.gif)
All URL's should start with a slash (ie: /catalog/images/blah.gif) or a a directory (ie: blah.gif).
If you have ANYTHING on an HTTPS: (SSL) page that references an HTTP:
address, IE won't display the lock icon. This includes Stylesheets and
How to get the credit card error messages to show up during checkout,
when using AuthorizeNet Consolidated for AIM 1.7 contribution and STS.
HOW TO CREATE PRODUCT-SPECIFIC TEMPLATES IN STS v2.01
Has anybody gotten the "multiple category templates" funtion
working? I've been trying for weeks now. Created the directories &
files, however they aren't getting picked up.
How to add Popup Images on product_info.php.html templates
Problem with the credit class/gift voucher contribution not displaying
a coupon code error during checkout
Help? | About DiamondSea
| Sign Up | Support
| Login |
Legal | Home
||Copyright © 2003. Any duplication without written permission prohibited. All Rights Reserved.|