Jump to content

paperlion

Members
  • Content count

    9
  • Joined

  • Last visited

Profile Information

  1. paperlion

    product codes coding

    I copied my home page along with my four existing product pages as sts_templates folder pages (index.php_0.html and index.php_01_00.html through index.php_04_00.html for the products pages. Now I would just type in codes where I want it on the new template pages, but I am not clear about this. If product codes are dynamically assigned, can they be locked if products are discontinued, so that item 3 doesn't now become item 2? Are there parameters for coding the products if they are selectively codable? Can I add a letter to the product code for color or size to help recognize the item just by looking at the code? Can I use dashes or the like in the product codes? If my original layout used submit buttons to add the item to a cart, what code would actually be used on the submit button's AREF tag? If product numbers, submit to cart, and go to cart functions are all that I want right now from the cart program, is this enough for the program to run? I've read through the docs and a lot of the forum and haven't seen these addressed. Thanks for you help.
  2. paperlion

    [contribution] Simple Template System (sts)

    Oops. Posted this to the general thread... Developing a new fascination for the potential of this new sts contrib. Haven't gotten to use it yet, but am very excited. This is my first dabbling with OSC though too, and am unsure of what the minimal page structure would be. My first idea was to just copy my home page along with my four existing product pages as sts_templates folder pages (index.php_0.html for the home page with the current product pg selector nav; and index.php_01_00.html, etc. through index.php_04_00.html for each of the products pages [each of these category pages has multiple products]). I actually did this. Now I was planning to either copy and paste code, or just type it in where I want it on the new template pages, but am not clear about it. Are there additional parameters for coding the products? Can I add a letter for color or size to help recognize the item just by looking at the code? Can I use dashes or the like? If my original layout used submit buttons to add the item to a cart, where is this product code actually generated in osc/sts? What code would actually be used on the submit button's AREF tag? If product numbers, submit to cart, and go to cart functions are all that I want right now from the cart program, is this enough for osc? If product codes are dynamically assigned, can they be locked if products are discontinued, so that item 3 doesn't now become item 2? These may sound like total newbie questions, but I've read through the docs and a lot of the forum and haven't seen these addressed, so maybe someone else will benefit from them too - besides over having a good laugh. :P
  3. paperlion

    [contribution] Simple Template System (sts)

    Developing a new fascination for the potential of this new sts contrib. Haven't gotten to use it yet, but am very excited. This is my first dabbling with OSC though too, and am unsure of what the minimal page structure would be. My first idea was to just copy my home page along with my four existing product pages as sts_templates folder pages (index.php_0.html for the home page with the current product pg selector nav; and index.php_01_00.html, etc. through index.php_04_00.html for each of the products pages [each of these category pages has multiple products]). I actually did this. Now I was planning to either copy and paste code, or just type it in where I want it on the new template pages, but am not clear about it. Are there additional parameters for coding the products? Can I add a letter for color or size to help recognize the item just by looking at the code? Can I use dashes or the like? If my original layout used submit buttons to add the item to a cart, where is this product code actually generated in osc/sts? What code would actually be used on the submit button's AREF tag? If product numbers, submit to cart, and go to cart functions are all that I want right now from the cart program, is this enough for osc? If product codes are dynamically assigned, can they be locked if products are discontinued, so that item 3 doesn't now become item 2? These may sound like total newbie questions, but I've read through the docs and a lot of the forum and haven't seen these addressed, so maybe someone else will benefit from them too - besides over having a good laugh. :P So thanks for you help.
×