How To Create Static Pages Using STS

[js28784]

Hello,

 

I use the STS contrib on my site and need to add about 7 different "static" pages.

 

I have the links to the pages built into the the template (ie: I have a button that links to guarantee.php).

 

But I would like for the static pages to display the category and cart that the current template includes.

 

Any thoughts on how to incorporate this?

 

Any advice would be appreciated greatly.

[dave111]

Just make copies of "shipping.php" and includes/languages/english/shipping.php

 

Rename them to "guarantee.php" and change any "shipping" to "guarantee" in the code for each file.

 

Then create your template page and name is "guarantee.php.html" put it in the includes/sts_templates folder.

[DiamondSea]

Or create the new pages as categories (if you want them to appear in your category box) and create a custom template page for that category.

 

- Brian

[shaunklink]

I actually figured this trick out on my own......hilarious that I happened to use shipping.php for it. I want to expand on this though.

 

My client wants the have the directory structure like so:

 

site.com/products/productname/

 

now the built in osCommerce product_info.php page is not enough, even with STS. What I need to do is create about 3-4 pages that expand on the product....I.e. Features page, specs page, image gallery page, etc.

 

how can I keep everything within the engine while retaining this new directory structure. Also, I don't want to use any of those SEO contribs.

 

what about just making static pages with buttons that are coded to send the same information to the engine.....I.e. My Account still just sends the user to account history, etc...

 

please help!

[DiamondSea]

I actually figured this trick out on my own......hilarious that I happened to use shipping.php for it.? I want to expand on this though.

 

My client wants the have the directory structure like so:

 

site.com/products/productname/

 

now the built in osCommerce product_info.php page is not enough, even with STS.

 

What sacrilege! :o :)

 

What I need to do is create about 3-4 pages that expand on the product....I.e. Features page, specs page, image gallery page, etc.

 

how can I keep everything within the engine while retaining this new directory structure.? Also, I don't want to use any of those SEO contribs.

 

what about just making static pages with buttons that are coded to send the same information to the engine.....I.e. My Account still just sends the user to account history, etc...

 

please help!

<{POST_SNAPBACK}>

 

You could try making 4 products for each page, and having separate templates for each one that shows the particular details for that page. It'd be a clumsy hack but might work if you don't have anything better to use.

 

- Brian

[shaunklink]

What sacrilege!  :o :)

You could try making 4 products for each page, and having separate templates for each one that shows the particular details for that page.  It'd be a clumsy hack but might work if you don't have anything better to use.

 

- Brian

<{POST_SNAPBACK}>

 

yes, it is sacrilege! but I'm desperate! I've been working on this site for about 2 months now and I'm starting to have weird dreams :P.

 

anyways, the dosn't quite work for me still. The problem is the product path. it would say "product_info.php?product_id=#" for each page.

 

go to http://www.i-muffs.com to see what I mean. My site is nothing like a regular osC site.

 

it's not all about funcitonality, its also about the little things, even directory structure. I only wish I could take every osc file and stick them in more directories.

 

also, the SEO contribs make a mess out of this site, otherwise I would just use those. The item name is very long, and when the SEO is on, my client dosn't like having a sentance in the URL...although, I kind of liked it :)

 

BTW. Brian.......thanks, I mean really.....thanks....STS is wonderful. I loved making my own $b oxes :) My only prblem with OSC is that it has way to many crazy table tags....whereas STS you can be responsible for your own mess.

[shaunklink]

BTW, for future reference, I merely made my own external pages with working code that interacts with the cart. Yes, it is not "PURE" as many would say, but so far, the cart stays full, and the user stays logged in...so I'm happy.