Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

bkellum

Pioneers
  • Posts

    4,854
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by bkellum

  1. No, what I am saying is that the add-on "OSC to CSS" has made so many modifications to the core of osCommerce that it really isn't osCommerce anymore. So, you really can't follow the installation instructions for STS. I haven't had the time to look at that contribution to see what would be needed to make the two compatible but as far as I see it now it would be one or the other but not both.
  2. Rob, There is a section in the STS User Manual that specifically covers this topic; Section 6.3 It is under the Tips and Tricks as it doesn't really relate to STS but it is assumed most STS site owners would benefit from this information.
  3. Dan, I don't know of any less harsh way of putting this so I apologize ahead of time... I think osCommerce as well as STS is out of your league. If you do not know what a css file is or even HTML, then there is no one there that can help you. You need step by step instructions on the very basic of web master skills so developing and maintaining an osCommerce site would be too daunting for you. STS is a great tool for shop owners who don't know PHP but want to maintain their site using the web skills that they are used to; considering these skills are up to par in maintaining a typical web site as well as an online ecommerce shop. You are expected to know HTML and CSS Styles at the very least. Then, it would be a great bonus to understand JavaScript and other cut and paste type programming. This forum is willing to answer your questions on how to use STS or assist in getting it installed on your shop but it is beyond the scope of this forum to teach you the necessary arts in web development. The links I had suggested in my reply to your original post would have been suffice for a web developer who has the basic skills of web development and was just starting out with STS. Good Luck and I wish you the best,
  4. STS was designed for osComemrce version 2.2, RC1, RC2 and RC2a. You are not using either.
  5. Dan, osCommerce pages are dynamic and the content is being pulled in from the database and/or scripts within the core code. STS allows you to make a single template to be used for all pages in your site or several templates for specific pages in your site as well as infoboxes etc. I would suggest that you take a look at the following link that has information for all new STS users: Important Links for STS Newbies
  6. Just so you're clear...you would do this simply by creating a "home page" template: index.php_0.html
  7. Checkout the solution that I use quite often as I'm sure it will meet your needs: Shopping Cart in Header (or anywhere for that matter). Post #4183
  8. It allows you to select via the admin any template themes you have uploaded to the STS Template folder. The engine allows you to use a template for infoboxes, specific pages, etc. or use one template page for the entire shop. You will be required to use whatever tools you have available to you to create your HTML, Flash, etc. pages that would be used as your template pages. Best way to find out what STS is about is to install it on a test site and scroll through the various sample template sets that are provided with the contribution. THEN, if you have any questions, post them in the designated STSv4 Forum (link in my signature below) so as not to have STS threads all over this forum. See you there,
  9. If the "themes" you are referring to are STS Template themes, then you would simply upload the new theme folder to your includes/sts_templates/ folder and then all you do from there is simply select what you them you want to use in the shop's admin via a nifty drop down menu. If the "themes" you are referring to are NOT STS Template themes but rather osCommerce (entire shop) themes, then you need to do some work. Take a look at my step my step for such a scenario
  10. Usually, the // double forward slash indicates an extra forward slash within your configure.php path settings and not related to STS.
  11. You would need to add your language to any language files included in the STS contribution. For example: admin/includes/languages/*your_language*/modules.php and admin/includes/languages/*your_language.php* and includes/languages/*your_language*/modules/sts/sts_default.php includes/languages/*your_language*/modules/sts/sts_index.php includes/languages/*your_language*/modules/sts/sts_popup_image.php includes/languages/*your_language*/modules/sts/sts_product_info.php You can use the files within any of the existing language folders/files to edit and modify to your desired language and then save it as the proper language file name.
  12. Try removing the 'box' from the code in the imageincartbox tag creation: $sts->start_capture(); require(DIR_WS_BOXES . 'manufacturers.php'); $sts->stop_capture ('manufacturers', 'box'); $sts->start_capture(); require(DIR_WS_BOXES . 'advsearch.php'); $sts->stop_capture ('advsearchbox', 'box'); $sts->start_capture(); require(DIR_WS_BOXES . 'imageincart.php'); $sts->stop_capture ('imageincartbox');
  13. This would have to do with one of your stylesheets. The class is productListing-heading and one of your stylesheets has a different setting other than font-size: 10px.
  14. Do any of the other contributions that you installed prior to STS modify the includes/classes/boxes.php file? If so, then you most likely did not merge the STS boxes.php file correctly. My thought to help you troubleshoot would be to upload the boxes.php file from the MS2 folder that came with STSv4.6.
  15. Install STSv4.6 and then select one of the sample templates to work with. Using the sample template, start merging in your custom HTML into it. Just keep in mind that the STS tags will bring in the dynamic content so for example, if you didn't want the Information infobox to appear, you would simply not include that STS tag. By the way, STS has it's own forum. Please use the link in my signature below (STSv4 Forum) to post all of your STS questions.
  16. There is no boxes.html in STS or osCommerce for that matter. Are you using a stock version of osCommerce?
  17. Thanks for posting back. :-) It gets easier from here onward.
  18. If you were using STS4.x or later, it would simply be a matter of uploading everything from the latest build. If you were using STS3.x or older, then you would need to remove most if not all of the previous STS installation, such as you have to remove the old STS code from several files in the catalog/includes folder: header.php, footer.php, application_bottom.php and application_top.php, then you can start installing the new STS. Keep in mind, you will need both the new STS file modifications as well as the existing file modifications from the latest version.
  19. Looks like you were simply missing the call to the default stylesheet and that would have taken care of your problem.
  20. Either something in your configure.php files are not setup correctly or you have made some modifications in the STS modules that is pointing to the wrong path.
  21. You have not completed the installation correctly. I have provided all of the files that you need so you could easily COMPARE them with the files that you edited manually to make sure you did the correct modifications to your shop.
  22. Two errors on your part: 1. Your configure.php files are not setup correctly as this is what will determine the site locations. 2. You have misconfigured the STS Default module and possibly the STS Popup Image module as well. Set everything back to the default settings and then test from there.
  23. The issue is a user error on your part. You have misconfigured the settings in the STS Default module. Change everything back to the default settings. For example: Files for normal template sts_user_code.php Base folder includes/sts_templates/ Template folder **select one from the dropdown menu** Default template file sts_template.html
  24. You did not upload the files from the STS folder. You need both sets of files!
  25. This is most likely from uploading the wrong application_top.php or sts.php in the wrong folder on your server.
×
×
  • Create New...