Jump to content

bkellum

Members
  • Content count

    4,854
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by bkellum

  1. For those experiencing problems using the download feature in osCommerce. Enable downloads in the admin/configure/downloads section of your store, Upload your product to the cataloag/downloads folder as a zip file (using no spaces in the name) Create a products page as you would normally for any product you sell Go to admin/catalog/product attributes page. Under "Product Options", create a new option called "Download" or something that you and your customer will recognize. In the same Product Attributes page, create a Option Value of "YEs" or "Only" or whatever. Still in the Product Attributes page, at the bottom of the page, you will find a drop down menu of each of your products. Find the product that you wish to offer as a download and select it. Under the Option Name, choose "Download" or whatever you used in step 4 above. Under Option Value, choose "yes" or whatever you used in step 5 above. Set your price for the product or leave blank. Skip the Prefix section. Type in the exact name of the download file as it is saved in your catalog/downloads folder as you did in step 2 above. Remember, no spaces in the filename and include the .zip extention. Set the number of days the purchased download will be available to your customer. Set the maximum amount of downloads tries you wish to grant to your customer. You should at the very least give your customer 2 tries, in case something happens to thier connection. Finally, click the "insert" button at the far right. Your product is now available for download. :thumbsup: Good Luck, Bill Kellum
  2. bkellum

    Contribution - New USPS mod for 2.2 shops

    DOH!!! This came one day too late for me :-( I just upgraded a client's USPS module manually. Thanks for uploading for others :-)
  3. Really anticipating v3.0!

  4. bkellum

    STS is working for v2.3.x ?

    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
  5. bkellum

    STSv4.6_1 and OsCommerce 2.3.1

    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.
  6. bkellum

    STS has me pulling out my hair

    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.
  7. bkellum

    [Contribution] STS v4

    /* 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:
  8. bkellum

    Using sts 4.6 on localhost

    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.
  9. bkellum

    [contribution] Simple Template System (sts)

    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.
  10. bkellum

    [contribution] Simple Template System (sts)

    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.
  11. bkellum

    [contribution] Simple Template System (sts)

    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.
  12. bkellum

    [contribution] Simple Template System (sts)

    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.
  13. bkellum

    [contribution] Simple Template System (sts)

    STS currently does not work with osc v2.3.1 unless you uninstall the stock template engine. STS will work with osc RC2a.
  14. bkellum

    [contribution] Simple Template System (sts)

    STS is not the problem. Check your installation of One Page Checkout.
  15. bkellum

    [Contribution] STS v4

    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).
  16. bkellum

    [Contribution] STS v4

    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.
  17. 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.
  18. bkellum

    STS Template tags does not work

    Try uninstalling STS via the STS Default Module and log out of the admin. Log back into the admin and then reinstall STS via the STS Default Module.
  19. bkellum

    Infoboxv5.4_in_header with STS

    Be sure the paths are correct for each link in the code I provided previously.... For example: "/create_account.php" - Add in your subfolder name if your store is not in the root of the site. Add a "$" at the end of the logoff tag: $logoff$
  20. bkellum

    Infoboxv5.4_in_header with STS

    Why not just simply add the form to anywhere you want in your STS Template? <!-- add this to your sts template file. ---> <div id="login"> <form action="[url="http://YOURSITE.COM/YourSiteStoreDirectory/login.php?action=process"]http://YOURSITE.COM/YourSiteStoreDirectory/login.php?action=process[/url]" method="post" name="login" > Login:<input type="text" name="email_address"/><br/> Password:<input type="password" name="password"/><br/> <a id="sign_in" onclick="login.submit()">Sign in</a> <a id="sign_up" href="/create_account.php">Sign up</a> <a id="forgot" href="/password_forgotten.php">Forgot?</a><br/> $logoff </form> </div> <!-- end of login --> Of course...you will need to replace " YOURSITE.COM/YourSiteStoreDirectory " with your actual URL and store directory (if not installed in the root).
  21. bkellum

    [Contribution] STS v4

    Are you simply transferring the local site to the remote site? What version of osC are you using? Is it the same version on both sites? This appears to be nothing more than a bad FTP transfer. Try uploading all of the files again or change FTP client software.
  22. bkellum

    [contribution] Simple Template System (sts)

    Jenny, The STS User Manaul tells you how to do this: When adding a new contribution to your store that adds a new infobox, you will need to define a new STS tag for the new infobox being created by that contribution. How to add a new infobox variable(tag) to STS: Add this code to sts_user_code.php $sts->start_capture(); require(DIR_WS_BOXES . 'infobox_name.php'); $sts->stop_capture('infobox_name', 'box'); The above would create a STS user tag called $infobox_name$. Place this tag anywhere in your template where you want this new box to appear. Change what you need to make it work for your specific box name. In the sample above, the new box being added was infobox_name.
  23. bkellum

    [Contribution] STS v4

    I just began playing with v2.3 last week and since then the code has already been changed regarding the tables.... So... Yes, STS will need to be updated to be used with v2.3. I have begun doing that but until the final release of v2.3, I really do not know what I will be working with.
  24. bkellum

    [contribution] Simple Template System (sts)

    Check your doctype for each template page.
  25. bkellum

    STS won't install

    Yes, oh really! Don't waste everyone's time by double posting. I answered your previous thread. Do you really think we provide 24 hour free support on this forum that you would get instantaneous responses?? Yes, you do have osCommerce....or you did. But, you installed OSC to CSS which is basically a fork (a spin off) of osCommerce. OSC to CSS makes so many changes to the core code of osCommerce that it is now incompatible with most other add-ons without making extensive changes to those as well. It is either "STS" or "OSC to CSS" unless you can find someone willing to make all of the necessary modifications for you to make them compatible. Don't misunderstand what I am saying... I am not saying that "OSC to CSS" is a bad add-on. What I am saying is that at this time, no one has bothered to make the two compatible with each other. They would probably be a nice marriage.
×