Jump to content
  • Checkout
  • Login
  • Get in touch


The e-commerce.


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by bkellum

  1. bkellum

    [contribution] Simple Template System (sts)

    1) Yes, but make a backup first. Depending upon your template needs, you may need your boxes.php file as well as your sts_user_code.php file if you happen to have these files customized to meet your old template. 2-3) You can continue to use your old template and I suggest moving it to ../includes/sts_templates/Old where "old" will be the name of the template set that holds your sts_template.html file (old template). 4) Your question tells me you really do not understand how STSv4.6 functions. Keep in mind that STS allows you to have as many template sets that you want and you can easily change between any of them via the drop down menu in the STS Default Module in the admin. With that said, each template set can have it's own stylesheet.css file and it should be located in the root of the template set folder (blue_hash, freeosc_009, freeosc_060, freeosc_061, multiple, single or your new addition: "Old"). It would be wise to review each of these template sets to see how you should name your templates, etc. That is what they are there for. Whatever you do, make sure you link to your stylesheet.css file within your template pages. For example, if you place your stylesheet.css file in the template folder "Old", then you would link to your stylesheet.css file in your template as so: <link rel="stylesheet" type="text/css" href="stylesheet.css"> <link rel="stylesheet" type="text/css" href="$templatedir$/stylesheet.css"> You can link as many stylesheets that you need. The first link is for the osC default stylesheet that is located in the shop's root folder. The second is the stylesheet specific to this template set. The STS variable $templatedir$ will use whatever template set you have selected via the drop down menu in the STS Default Module in the admin.
  2. bkellum

    STS with Dynamenu?

    Sure, just look up the files in the STSv4 Power Pack site. It's all there for you to sample.
  3. bkellum

    Install Question STS

    So, if you get the Fatal error: Cannot redeclare do_magic_quotes.gpc() [...] then note which php file you called when you got the error, and make sure you haven't mistakenly copied the same file to the languages folder. These errors usually mean you copied a file to the wrong folder and in the process may have inadvertantly copied over a necessary file of the same name (but in a different folder).
  4. bkellum

    problems installing STS....

    Please post all STS related Support questions in the proper STSv4 Support Thread. The link is posted on the contribution page, listed in the STS User Manual as well as listed in my signature below. ***This thread is Closed****
  5. You missed the point...."I'm not trying to change the text". However, I would agree that the Page Editor contribution does work quite nicely with the Simple Template System v4.6.
  6. This could only happen if you either did not complete the install correctly (including bad uploads from a poor FTP Client software that you used) or you mis-configured the STS Modules in the admin. If the latter is the case, simply use the default settings and change only the following in the STS Default Module: 1. Use Template: TRUE 2. Template Folder: select the blue_hash or any other template from the drop down 3. That's it. Test.
  7. bkellum

    [Contribution] STS v4

    Hello, this can be easily done by simply removing the the echo statement in the template or modifying your "Store Name" in the admin. <div id="website_name"><?php echo STORE_NAME; ?></div> You could remove the above code entirely from your template and add anything your want in your header. Take a look at the multiple template set to see an example on how to easily create a "header" template that would be used for all pages in your shop.
  8. bkellum

    [contribution] Simple Template System (sts)

    This is NOT necessary and SHOULD be avoided. Try using $templatedir$/stylesheet.css (notice the beginning and ending stop character $). If you are requiring a stop end character (strongly suggested) for your tags, then you need a stop character for ALL of your tags consistently. So, if your template uses the following code at the top, you should be adding the stop end character to each of your STS tags: <?php DEFINE ('STS_END_CHAR', '$'); ?> <?php DEFINE ('STS_CONTENT_END_CHAR', '$'); ?> Hope this helped you out,
  9. bkellum

    [Contribution] STS v4

    Be sure to view each of the documents in the "docs" folder. They explain what you need to do to enable STS. Your issue may be as simple as "turning on" STS in the STS Default Module. Respond back and let me know.
  10. bkellum

    [Contribution] STS v4

    Like I said, check your upload as you may have not uploaded ALL OF THE FILES CORRECTLY. Use a File Comparison Tool to make sure.
  11. bkellum

    [Contribution] STS v4

    STS is very easy to install; probably the most easiest of all other contributions. If you are having problems, the best way to find the cause is to purchase a good file comparison tool such as Beyond Compare (or download one of the open source equals such as WinMerge). Use this tool to compare your files that you installed with the files that came with the contribution. Compare the files from the STS folder as well as the "Files for RC2" folder. Also, invest in a reliable FTP client software program to upload your files completely and accurately.
  12. bkellum

    [contribution] Simple Template System (sts)

    If it is a fresh install, simply upload the files from the STS folder & the "Files for RC2" folder. Done. Couldn't be any easier. Try using a well known FTP Client software to upload your files as this could be your issue as well.
  13. bkellum

    [contribution] Simple Template System (sts)

    You did not complete the STS installation. Compare your files with the files from the contribution (STS folder and Files for RC2 folder).
  14. bkellum

    [Contribution] STS v4

    Tracy, I would start with it being a SEO Link problem. Turn off that and then clean your cache and then see if it works or not.
  15. bkellum

    Create templates for different languages

    STS Support Thread would be a good start....this has been answered many times there.
  16. bkellum

    STS templae help

  17. Yep, it's a big problem for those who do not post in the STS Support Thread. Hmmmm....the link is in the STS User Manual as well as in my signature below. A lot of good answers in that thread that can be easily googled for.
  18. bkellum

    [contribution] Simple Template System (sts)

    I just do not know how to explain it any other way than what I already have.
  19. bkellum

    [contribution] Simple Template System (sts)

    Yes. Take a look at the product_info.php.html file that came with the contribution to see where you went wrong. Make sure you have everything within the form tags. Also, you will need to turn on the proper STS modules in the admin. Also, make sure you did not make the newbie mistake of turning "Enable Search Engine Friendly URL's" to true in the admin. This should never be enabled as the results will be unpredictable behavior such as what you are experiencing.
  20. bkellum

    [contribution] Simple Template System (sts)

    This will not have anything to do with STS as STS does not modify any of the configure.php files. You need to login to your host account and change the permissions to that file (not through FTP).
  21. bkellum

    [Contribution] STS v4

    I would suggest you upload this contribution to get rid of your infobox images. Also, look in the STS User Manual in Chapter 7 on how to create a specific infobox template (2 parts, one header, one content) to allow you to create a blank header (without the $headertext tag) in order to prevent the header text from displaying in that particular infobox.
  22. bkellum

    [contribution] Simple Template System (sts)

    You must have a much older version (prior to STSv3) so you will not have anything in the admin but you will have configuration files in your includes/configure.php. You should remove each line of STS code in your configure.php. You should also remove all STS lines of code from the other files in your shop. You could do this be using a file comparison tool to compare your shop with a stock RC2a shop.
  23. bkellum

    [contribution] Simple Template System (sts)

    What version of STS are you using now? Is STS even installed at the moment? I wouldn't recommend installing anything until you figure out what the problem is that is causing your blank page in both the admin and the front end. If you have STS installed now, then you need to go into the admin and turn it off to see if that takes care of your blank page. I'm thinking this is not realted to STS at all but rather a fouled osC RC2a upgrade. Try your RC2a upgrade again or install RC2a from scratch and then install STSv4.6.
  24. bkellum

    Featured Product Support v1.5.4

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

    [contribution] Simple Template System (sts)

    You should enable the following modules: STS Default STS Index Then, select your template folder that you want to use for all of your templates in the STS Default module. Then, create your template that you need using the following naming syntax below and save it in the template folder that you selected above: TIP Here is a quick rundown of common template names: sts_template.html= Default template [*]index.php.html = Default Category template (used for all category pages that do not have a specific template page created for it – if you didn’t have this template, STS would use sts_template.html). [*]index.php_0.html = Home page template [*]index.php_x.html = Specific category template where x = the category ID. This template will create your custom category template(s) that you are interested in. [*]index.php_x_y.html = Specific subcategory template where x = the category ID and y = the subcategory ID [*]product_info.php.html = Default Product template (used for all products, in all categories, if no specific product template is found). [*]product_info.php_c23.html = Product template for all products in a specific category (23 in this example – change to the category ID needed) [*]product_info.php_23.html = CONTENT template for product ID 23. All content template should be saved in the SGP/content/ folder. Review the sample content template provided in the STS template “full/content” folder. The STS Module Product Info must be enabled in order to use this STS feature. This template is not recommended unless you really know what you are doing since you would need to make modifications to it if you ever added new osCommerce contributions to your shop. [*]popup_image.php.html = Template for the product popup image. [*]index.php.mfr.html = Default Manufacturer template page (used for all manufacturer pages that do not have a specific template page created for it - if you didn’t have this template, STS would use sts_template.html). [*]index.php.mfr_x.html = Specific Manufacturer template where x = the manufacturer ID.