Latest News: (loading..)

bkellum

Members
  • Content count

    4,854
  • Joined

  • Last visited

  • Days Won

    5

bkellum last won the day on July 24 2010

bkellum had the most liked content!

About bkellum

  • Birthday December 29

Profile Information

  1. DOH!!! This came one day too late for me :-( I just upgraded a client's USPS module manually. Thanks for uploading for others :-)
  2. It can be done but you need to remove the current template system that was introduced in Osc v.2.3. It really isn't that serious of a modification if you follow the upgrade path from Osc v.2.2 to Osc v.2.3 (leaving out the changes that apply to the template system of course). I would love to submit my (incomplete) work for STSv5 that would be compatible with Osc v.2.3.1 but now that Osc v3 will be available, it really isn't worth it at this time. I'll wait to see how everything works with Osc v.3 first and then go from there. Here is the link with details on how to make STSv4.6 compatible with Osc v2.3
  3. Thanks Mark. It can be done but you need to remove the current template system that was introduced in Osc v.2.3. It really isn't that serious of a modification if you follow the upgrade path from Osc v.2.2 to Osc v.2.3 (leaving out the changes that apply to the template system of course). I would love to submit my (incomplete) work for STSv5 that would be compatible with Osc v.2.3.1 but now that Osc v3 will be available, it really isn't worth it at this time. I'll wait to see how everything works with Osc v.3 first and then go from there.
  4. STSv4.6 does not work out of the box with osCv2.3. You need to make some modifications. Take a look at this post in the STS Support Thread.
  5. /* The following code is a sample of how to add new boxes easily. Use as many blocks as you need and just change the block names. $sts->start_capture(); require(DIR_WS_BOXES . 'new_thing_box.php'); $sts->stop_capture('newthingbox', 'box'); // 'box' makes the system remove some html code before and after the box. Otherwise big mess! Note: If $sts->stop_capture('newthingbox', 'box') is followed by $sts->start_capture, you can replace both by $sts->restart_capture('newthingbox', 'box') Also, make sure if you are using stop end characters as you stated above, $builderbox$, that all of your tags are using them as well. Otherwise, simply use $builderbox instead. Also, See this post:
  6. Yes. Configuring the localhost correctly is up to you. Most beginners error by using a default out of the box configuration for bundles such as Xamp which produces errors for a lot of PHP scripts such as osCommerce.
  7. This is most likely at the very bottom of most user's priority list as it does not cause any operational issues with osCommerce or STS.
  8. STSv4.6 will work with osc v2.3.1 as long as you remove the stock osCommerce template engine. You do this by reverse engineering the code by undoing the changes suggested in the osC RC2a to osCv2.3.1 upgrade instructions.
  9. It would have been better to uninstall the older version of STS and then install v4.6. Try this: Use a file comparison tool such as Beyond Compare to compare your current setup with the STSv4.6 contribution. Remove any STS files/code that is not part of STSv4.6. Note: STSv4.6 does not have any issues such as you are experiencing.
  10. The correct location for the upload would have the STS Power Pack site, a site dedicated to all STS addons such as your PDF uploader for STS.
  11. STS currently does not work with osc v2.3.1 unless you uninstall the stock template engine. STS will work with osc RC2a.
  12. STS is not the problem. Check your installation of One Page Checkout.
  13. The solution is listed in the STS User Manual as well as examples in the STS Power Pack download site (link in my signature below).
  14. For those who can't wait for the STSv5 release that is compatible with osCv2.3.1, I suggest the following: 1. upgrade to osCv2.3.1 using the upgrade guide but leave out the default osCommerce template upgrades. 2. Then, install STSv4.6 using the "manual" method within the STSv4.6 install instructions. What the above will get you is the following: 1. The latest osCommerce stable build (minus the default template engine) 2. The latest version of the Simple Template System. Note: Many are finding the default template engine that comes with osCv2.3.1 very daunting and limiting. By leaving out the template engine, you still get all of the great security upgrades that osCv2.3.1 brings as well as a very easy to use template system (STSv4.6). :( I have experienced a string of tragedies in the last 3 months that has really taken up my time, hence, the long wait for STSv5. :thumbsup: If anyone wants to collaborate on bringing STSv5 to a reality, and contribute, here is what should be considered: 1. STSv5 install needs to focus on either disabling the default template engine in osCv2.3.1, or better yet, configure STSv5 to take advantage of the new template engine and work along side of it (bring STS functionallity to the template engine). 2. The latter suggestion would continue the strong tradition of keeping STS an on/off option in the admin, meaning that if you want to see what your shop looks like without STS, just simply turn it off in the admin and then the default template engine would work just like a stock osCv2.3.1 shop. The other benefit of this is that once the bulk of the other contributions are upgraded to work with osCv2.3.1, then STSv5 would not conflict with them. Yet, an even better scanario would be to have an either/or option in the admin to have STSv5 work along side of the default template engine or alone as the current STSv4.6 does. I metion this only because some designers may not want to use the grid system that comes with the default template engine and would rather stick with what they know, which is what makes STS so great anyway. 3. Redo all of the sample templates to work with STSv5/osCv2.3.1. 4. Consider droping support for older versions of osC (before v2.3.1). I don't recommend this as there is a huge shop base out there built on older versions of osCommerce. If needed, you can send me your work/email contact info via a private message in this forum.
  15. First off, if you have been reading in the STS Forum, Why not post all of the above there?? The Byte Order Mark is an old relic which is mostly caused by the editor that you are using to create your pages. Dig deep into the settings of your editor and change the settings that would cause the BOM to display. This mostly happens with Microsoft Front Page or Microsoft Expression Web. Both editors allow you to modify the settings in order to remove the BOM. See you in the STS Forums.