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!

Community Reputation

31 Excellent

About bkellum

  • Birthday December 29

Profile Information

  • Real Name
    Bill Kellum
  • Gender
    Male
  • Location
    Chicago

Contact Methods

  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. Lisa, :thumbsup: This doesn't have anything to do with osc_sec but it still needs to be done: Change the name of your admin folder to something other than admin!! Most of the osCommerce exploits are looking for the admin folder. Keep in mind, that once you rename the admin folder, you will also need to change the admin references in both of the configure.php files. Regarding the header not sent error message, look for any white space that occures after the very last ?> in any of the php files that you may have altered.
  3. Yes, it is possible. Unless you check all of your files and database, you won't know for sure.
  4. Lisa, This is most likely due to an installation issue. Check each of the files that you modified to be sure you did not add an extra "space" at the beginning or end of the file.
  5. 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
  6. 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.
  7. 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.
  8. /* 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:
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. STS currently does not work with osc v2.3.1 unless you uninstall the stock template engine. STS will work with osc RC2a.
  15. STS is not the problem. Check your installation of One Page Checkout.