[Contribution] STS v4

[bkellum]

By following the guide above, I was able to create a new page (newpage.php), the sts tag ($newpage), and the link to the page by adding the $newpage sts tag in my default template. It worked great!

 

:blink: I am having problems creating a template for the newpage.php. I created the template newpage.php.html but when I click on the link to the newpage, the default template is being used instead of the newpage.php.html template. :blink:

 

Anyone know why this is doing this? Did I miss something? Thanks for any help.

STSv4.4 BUG REPORT***

OK, Thanks to Arnaud (nanouchman) for this find. It will fix Bob's problem above.

 

Open the includes/modules/sts/sts_default.php file.

Find:

if (strstr($scriptbasename, "popup") || strstr($scriptbasename, "info_shopping_cart")) {
return ''; // We don't use template for these scripts

$check_file = STS_TEMPLATE_DIR .$scriptbasename . ".html";

if (file_exists($check_file)) return $check_file;

 }

Replace with (you will remove the brackets):

if (strstr($scriptbasename, "popup") || strstr($scriptbasename, "info_shopping_cart"))
  return ''; // We don't use template for these scripts

$check_file = STS_TEMPLATE_DIR .$scriptbasename . ".html";

if (file_exists($check_file)) return $check_file;

If you leave the brackets "as is", then you will experience the same problem as in Bob's post above.

Thanks again Arnaud!! Great bug catch!!! :- :blink: :thumbsup: :thumbsup:

[Guest]

Sounds good Jason. What finally solved your problem? Was it my solution or something else? Thanks for the follow up post.

 

Hi bill .

 

it works after following your solution.

 

thanks for your help.

 

regards

jason

[Guest]

I'm using STS 4.4 . I have a question in regards of using infobox templates. When I set " use template for infoboxes = ture " the header text of infobox disappeared .

 

 

I had not modified the infobox.php.html yet . I can see $headertext in infobox.php.html . don't know why it did not work.

 

when i set " Use template for infoboxes = false " everythiing o.k.

 

 

any idea. what should I check ?

 

regards

jason

[Guest]

I'm using STS 4.4 . I have a question in regards of using infobox templates. When I set " use template for infoboxes = ture " the header text of infobox disappeared .

 

 

I had not modified the infobox.php.html yet . I can see $headertext in infobox.php.html . don't know why it did not work.

 

when i set " Use template for infoboxes = false " everythiing o.k.

 

 

any idea. what should I check ?

 

regards

jason

 

i found the answer and solve the problem , thanks !

[Guest]

Hi all,

 

When I insert the placeholders into the blank temp I get the light blue box around each infobox. I have found and modified the gif's on the bottom, left and right sides, but where it says "catagories" it is still light blue. What is that gif called and where is it located?

 

Thanks,

Dano

[bkellum]

Hi all,

 

When I insert the placeholders into the blank temp I get the light blue box around each infobox. I have found and modified the gif's on the bottom, left and right sides, but where it says "catagories" it is still light blue. What is that gif called and where is it located?

 

Thanks,

Dano

Dano, that is not a graphic file but rather a cell background color. You can get rid of it completely or change it to a different color. Look in the HTML table in the infobox template to modify this.

[Guest]

$sts->start_capture();
echo "\n<!-- Start Category Menu -->\n";
echo tep_draw_form('goto', FILENAME_DEFAULT, 'get', '');
echo tep_draw_pull_down_menu('cPath', tep_get_category_tree(), $current_category_id, 'onChange="this.form.submit();"');
echo "</form>\n";
echo "<!-- End Category Menu -->\n";
$sts->stop_capture('catmenu');

 

I'm looking to create custom info boxes.

Is this what I need to modify?

Can I just make a gif and insert it in ('goto', FILENAME_DEFAULT, 'get', '')?

 

Thanks,

Dan

[Guest]

Dano, that is not a graphic file but rather a cell background color. You can get rid of it completely or change it to a different color. Look in the HTML table in the infobox template to modify this.

 

Ah...okay Bill. Will give it a go!

 

Thanks again,

dan

[Guest]

I get the error :

 

Template file does not exist: [includes/sts_templates/test/boxes/infobox_header.php.html]Template file does not exist: [includes/sts_templates/test/boxes/infobox.php.html]

 

 

Default template (v2.0.0)

 

Use Templates?

true

 

Code for debug output

debug

 

Files for normal template

sts_user_code.php

 

Base folder

includes/sts_templates/

 

Template folder

test

 

Default template file

sts_blank_template.html

 

Use template for infoboxes

true

 

That file was not included in the zip file. What give?

[bkellum]

Dan,

You are still using the "Test" template folder. This folder is the default "out of the box" template folder used to make sure the installation went OK and for you to get familiar with the STS system. Once you are ready to start creating your own templates, you should either create your own template folder or use the "full" template folder.

The "full" template folder has additional sub-folders such as "boxes", "content", etc.

 

The User Manual instructs you in order to use the template features for infoboxes, you need to use a template folder other than the "test" folder, and this new template folder must include the sub-folder "boxes".

 

So...when creating your infobox templates, you must save them in "sts_templates/my_templates/boxes" folder.

 

Hope this helps,

Bill Kellum

[Guest]

Alright...

 

Never mind that.

 

I have another fresh install. A fresh backup.

 

I'm getting a bit frustrated:)

 

What files do I need to modify to create a navigation similar to this

 

Thanks,

Dan

[Guest]

Dan,

You are still using the "Test" template folder. This folder is the default "out of the box" template folder used to make sure the installation went OK and for you to get familiar with the STS system. Once you are ready to start creating your own templates, you should either create your own template folder or use the "full" template folder.

The "full" template folder has additional sub-folders such as "boxes", "content", etc.

 

The User Manual instructs you in order to use the template features for infoboxes, you need to use a template folder other than the "test" folder, and this new template folder must include the sub-folder "boxes".

 

So...when creating your infobox templates, you must save them in "sts_templates/my_templates/boxes" folder.

 

Hope this helps,

Bill Kellum

 

Got it.

 

Can I just create a new blank HTML file in /full ?

 

And I'm still confused as to what files need to be edited to make $categorybox toggle a fully custom/transparent look.

 

How might I just draw a layer on the left of the template, insert a custom background image, and implement placeholders with transparent backgrounds?

 

Check out that link I provide above. A good example of what I am looking for.

 

Thanks Bill,

Dan

[bkellum]

Alright...

 

Never mind that.

 

I have another fresh install. A fresh backup.

 

I'm getting a bit frustrated:)

 

What files do I need to modify to create a navigation similar to this

 

Thanks,

Dan

Dan, you may be interested in the following contribution for the category box enhancement:

http://www.oscommerce.com/community/contributions,885

[bkellum]

Got it.

 

Can I just create a new blank HTML file in /full ?

 

And I'm still confused as to what files need to be edited to make $categorybox toggle a fully custom/transparent look.

 

How might I just draw a layer on the left of the template, insert a custom background image, and implement placeholders with transparent backgrounds?

 

Check out that link I provide above. A good example of what I am looking for.

 

Thanks Bill,

Dan

Dan, keep in mind that the stylesheet.css file also controls the look of the infoboxes. You can add the following:

.infoBoxContents {
 background: transparent;

The above was part of the STSv4.3.3 User Manual but was taken out of the STSv4.4 User Manual for some reason. I find it very helpul in customizing your infoboxes so that they better match your design.

 

Hope this has helped,

[Guest]

Dan, you may be interested in the following contribution for the category box enhancement:

http://www.oscommerce.com/community/contributions,885

 

Bill,

 

I would rather just keep it simple for right now, and not show subcategories, although that contribution is of interest.

 

What I wanted to point out with that link was the custom navigation. I am having an extremely hard time finding the exact files that need to be modified

 

I opened the sts_template.html in the /full folder

 

Selected all, deleted it. Added a logo layer, inserted the logo; added a spacer/topnav layer, insterted the background image; added a leftnav layer inserted $categorybox....those actions produce :

 

 

Say I want just the catagory names to show and not "Catagories", not the blue, nor the grey...what files would I need to modify?

 

I really appreciate your insight! I'm learning!

 

-Dan

[bkellum]

Bill,

Say I want just the catagory names to show and not "Catagories", not the blue, nor the grey...what files would I need to modify?

 

I really appreciate your insight! I'm learning!

 

-Dan

Dan, this is an easy one...

Create a new infobox template based on the sample "infobox.php.html" infobox template. Name this new template "infobox_categories.php.html".

Now leave out the $headertext tag but keep the $contents tag. This will pull in the PHP content of the categories.php infobox script minus the heading "Categories".

 

Now if you edit your stylesheet settings for the following:

TD.infoBoxHeading {
background: transparent;

.infoBoxContents {
 background: transparent;

You will be able to add the box into your design with no lingering stock osCommerce style properties hanging around messing up your design.

[bkellum]

You will also want to either come up with your own corner gif files or use transparent corner gif files.

Here are some transparent gif files for you:

http://www.oscommerce.com/community/contributions,4764

 

Have fun,

Bill Kellum

 

Dan, this is an easy one...

Create a new infobox template based on the sample "infobox.php.html" infobox template. Name this new template "infobox_categories.php.html".

Now leave out the $headertext tag but keep the $contents tag. This will pull in the PHP content of the categories.php infobox script minus the heading "Categories".

 

Now if you edit your stylesheet settings for the following:

TD.infoBoxHeading {
background: transparent;

.infoBoxContents {
 background: transparent;

You will be able to add the box into your design with no lingering stock osCommerce style properties hanging around messing up your design.

[Guest]

I just about got it....

 

I'm having trouble with the transparency of the content background.

 

 

Here is my new infobox_categories.php.html :

 

<table width="100%" border="0" cellspacing="0" cellpadding="0" style="border-collapse: collapse">
 <tr>
<td width="11">
<img border="0" src="images/infobox/corner_left.gif" width="11" height="14"></td>
<td class="infoBoxHeading" width="1428"> </td>
<td width="11" background="images/infobox_04.gif" style="background-repeat: norepeat">
<img border="0" src="images/infobox/corner_right.gif" width="11" height="14"></td>
 </tr>
</table>
<table width="100%" border="0" cellspacing="0" cellpadding="0" bgcolor="#FFFFFF" style="border-collapse: collapse" bordercolor="#FFFFFF">
 <tr>
<td bgcolor="#FFFFFF"> </td>
<td bgcolor="#FFFFFF">$content</td>
<td> </td>
 </tr>
 <tr>
<td width="30"> </td>
<td width="100%"> </td>
<td width="31"> </td>
 </tr>
</table>

 

My stylesheet.ccs :

 

/*
 $Id: stylesheet.css,v 1.56 2003/06/30 20:04:02 hpdl Exp $

 osCommerce, Open Source E-Commerce Solutions
 http://www.oscommerce.com

 Copyright (c) 2003 osCommerce

 Released under the GNU General Public License
*/

.boxText { font-family: Verdana, Arial, sans-serif; font-size: 10px; }
.errorBox { font-family : Verdana, Arial, sans-serif; font-size : 10px; background: #ffb3b5; font-weight: bold; }
.stockWarning { font-family : Verdana, Arial, sans-serif; font-size : 10px; color: #cc0033; }
.productsNotifications { background: #f2fff7; }
.orderEdit { font-family : Verdana, Arial, sans-serif; font-size : 10px; color: #70d250; text-decoration: underline; }

BODY {
 background: #ffffff;
 color: #000000;
 margin: 0px;
}

A {
 color: #000000;
 text-decoration: none;
}

A:hover {
 color: #AABBDD;
 text-decoration: underline;
}

FORM {
display: inline;
}

TR.header {
 background: #ffffff;
}

TR.headerNavigation {
 background: #bbc3d3;
}

TD.headerNavigation {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
 background: #bbc3d3;
 color: #ffffff;
 font-weight : bold;
}

A.headerNavigation { 
 color: #FFFFFF; 
}

A.headerNavigation:hover {
 color: #ffffff;
}

TR.headerError {
 background: #ff0000;
}

TD.headerError {
 font-family: Tahoma, Verdana, Arial, sans-serif;
 font-size: 12px;
 background: #ff0000;
 color: #ffffff;
 font-weight : bold;
 text-align : center;
}

TR.headerInfo {
 background: #00ff00;
}

TD.headerInfo {
 font-family: Tahoma, Verdana, Arial, sans-serif;
 font-size: 12px;
 background: #00ff00;
 color: #ffffff;
 font-weight: bold;
 text-align: center;
}

TR.footer {
 background: #bbc3d3;
}

TD.footer {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
 background: #bbc3d3;
 color: #ffffff;
 font-weight: bold;
}

.infoBox {
 background: #b6b7cb;
}

.infoBoxContents {
 background: #f8f8f9;
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
}

.infoBoxNotice {
 background: #FF8E90;
}

.infoBoxContents {
 background: transparent;
 font-family: Verdana, Arial, sans-serif;
 font-size: 24px;
}

TD.infoBoxHeading {
background: transparent;
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
 font-weight: bold;

 color: #ffffff;
}

TD.infoBox, SPAN.infoBox {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
}

TR.accountHistory-odd, TR.addressBook-odd, TR.alsoPurchased-odd, TR.payment-odd, TR.productListing-odd, TR.productReviews-odd, TR.upcomingProducts-odd, TR.shippingOptions-odd {
 background: #f8f8f9;
}

TR.accountHistory-even, TR.addressBook-even, TR.alsoPurchased-even, TR.payment-even, TR.productListing-even, TR.productReviews-even, TR.upcomingProducts-even, TR.shippingOptions-even {
 background: #f8f8f9;
}

TABLE.productListing {
 border: 1px;
 border-style: solid;
 border-color: #b6b7cb;
 border-spacing: 1px;
}

.productListing-heading {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
 background: #b6b7cb;
 color: #FFFFFF;
 font-weight: bold;
}

TD.productListing-data {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
}

A.pageResults {
 color: #0000FF;
}

A.pageResults:hover {
 color: #0000FF;
 background: #FFFF33;
}

TD.pageHeading, DIV.pageHeading {
 font-family: Verdana, Arial, sans-serif;
 font-size: 20px;
 font-weight: bold;
 color: #9a9a9a;
}

TR.subBar {
 background: #f4f7fd;
}

TD.subBar {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
 color: #000000;
}

TD.main, P.main {
 font-family: Verdana, Arial, sans-serif;
 font-size: 11px;
 line-height: 1.5;
}

TD.smallText, SPAN.smallText, P.smallText {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
}

TD.accountCategory {
 font-family: Verdana, Arial, sans-serif;
 font-size: 13px;
 color: #aabbdd;
}

TD.fieldKey {
 font-family: Verdana, Arial, sans-serif;
 font-size: 12px;
 font-weight: bold;
}

TD.fieldValue {
 font-family: Verdana, Arial, sans-serif;
 font-size: 12px;
}

TD.tableHeading {
 font-family: Verdana, Arial, sans-serif;
 font-size: 12px;
 font-weight: bold;
}

SPAN.newItemInCart {
 font-family: Verdana, Arial, sans-serif;
 font-size: 10px;
 color: #ff0000;
}

CHECKBOX, INPUT, RADIO, SELECT {
 font-family: Verdana, Arial, sans-serif;
 font-size: 11px;
}

TEXTAREA {
 width: 100%;
 font-family: Verdana, Arial, sans-serif;
 font-size: 11px;
}

SPAN.greetUser {
 font-family: Verdana, Arial, sans-serif;
 font-size: 12px;
 color: #f0a480;
 font-weight: bold;
}

TABLE.formArea {
 background: #f1f9fe;
 border-color: #7b9ebd;
 border-style: solid;
 border-width: 1px;
}

TD.formAreaTitle {
 font-family: Tahoma, Verdana, Arial, sans-serif;
 font-size: 12px;
 font-weight: bold;
}

SPAN.markProductOutOfStock {
 font-family: Tahoma, Verdana, Arial, sans-serif;
 font-size: 12px;
 color: #c76170;
 font-weight: bold;
}

SPAN.productSpecialPrice {
 font-family: Verdana, Arial, sans-serif;
 color: #ff0000;
}

SPAN.errorText {
 font-family: Verdana, Arial, sans-serif;
 color: #ff0000;
}

.moduleRow { }
.moduleRowOver { background-color: #D7E9F7; cursor: pointer; cursor: hand; }
.moduleRowSelected { background-color: #E9F4FC; }

.checkoutBarFrom, .checkoutBarTo { font-family: Verdana, Arial, sans-serif; font-size: 10px; color: #8c8c8c; }
.checkoutBarCurrent { font-family: Verdana, Arial, sans-serif; font-size: 10px; color: #000000; }

/* message box */

.messageBox { font-family: Verdana, Arial, sans-serif; font-size: 10px; }
.messageStackError, .messageStackWarning { font-family: Verdana, Arial, sans-serif; font-size: 10px; background-color: #ffb3b5; }
.messageStackSuccess { font-family: Verdana, Arial, sans-serif; font-size: 10px; background-color: #99ff00; }

/* input requirement */

.inputRequirement { font-family: Verdana, Arial, sans-serif; font-size: 10px; color: #ff0000; }

[TracyS]

Hi Bill,

 

Got another "fun" question :blush:

 

I've been scouring the forums for this - but so far I've not found much, and what I have found I'm not sure how to implement :huh:

 

I have this link:

<?php echo '<a href="' . tep_href_link(FILENAME_DEFAULT, '', 'NONSSL') . '">' . tep_image_button('button_continue.gif', IMAGE_BUTTON_CONTINUE) . '</a>'; ?>

 

And I want to function as a "back" button (just like the browsers back button) rather than just dump you back at the homepage. It is in the Customer Testimonials contrib - so if someone clicks to read a full testimony or read all testimonials for that particular product, etc.... they go to a new page with that info and at the bottom of the page is this "Continue" button. I don't want people who leave a product page to read the testimonials to then get dumped out to the home page when they click "Continue" - I want it to take them back to the product they were just viewing.

 

I found this :

Either way, here is some code for you to mess around with that may be the solution to your problem:

In shopping_cart.php, replace:

 

$back = sizeof($navigation->path)-2;

 

with

 

 

$back = sizeof($navigation->path)-3;

 

 

In the above scenario, the continue button will bring the customer back to the category or listing they were last viewing, before adding a product to their cart.

 

I'm sure you could play around with this code to get it to do what you are looking for. I'm sorry I couldn't give you the exact code since I wasn't really sure what you were wanting to do. I'm on pain killers at the moment for a recent hernia surgery so things aren't so clear for me. blink.gif

 

Hope this helps,

 

Bill Kellum

 

Which makes it appear as though there should be a way to do this - but I have not the slightest idea how to implement that in this particular situation :huh: :blush:

 

Any thoughts on how to make this particular link function as a back button?

 

Thanks!

[TracyS]

Hi Bill,

 

Got another "fun" question :blush:

 

I've been scouring the forums for this - but so far I've not found much, and what I have found I'm not sure how to implement :huh:

 

I have this link:

<?php echo '<a href="' . tep_href_link(FILENAME_DEFAULT, '', 'NONSSL') . '">' . tep_image_button('button_continue.gif', IMAGE_BUTTON_CONTINUE) . '</a>'; ?>

 

And I want to function as a "back" button (just like the browsers back button) rather than just dump you back at the homepage. It is in the Customer Testimonials contrib - so if someone clicks to read a full testimony or read all testimonials for that particular product, etc.... they go to a new page with that info and at the bottom of the page is this "Continue" button. I don't want people who leave a product page to read the testimonials to then get dumped out to the home page when they click "Continue" - I want it to take them back to the product they were just viewing.

 

I found this :

Which makes it appear as though there should be a way to do this - but I have not the slightest idea how to implement that in this particular situation :huh: :blush:

 

Any thoughts on how to make this particular link function as a back button?

 

Thanks!

 

LOL - well, now that I've asked the question I think I've found the answer :blush:

 

I changed the above link to this:

<a href="java script:history.back(1)"><?php echo tep_image_button('button_continue.gif', IMAGE_BUTTON_CONTINUE); ?></a>

 

It appears to be working the way I wanted it to, and it does not seem to be losing the Session ID - YAY! Do you see anything in the above link that you know causes problems?

 

PS - the forum seems to want to separate javascript into two words when I post this - it's only one word in my link

Edited March 8, 2007 by TracyS

[m45537]

First post, here goes...

 

I have read about the power of STS and I want to learn more and figure out how to use this contribution. In an attempt to install 4.3.3 I have this question...

 

If I have the following code in my catalog/includes/header.php file does that indicate that a previous version of STS is installed?

 

// STS: ADD

$sts_block_name = 'applicationtop2header';

require(STS_RESTART_CAPTURE);

// STS: EOADD

 

Thanks,

 

Mike

[bkellum]

First post, here goes...

 

I have read about the power of STS and I want to learn more and figure out how to use this contribution. In an attempt to install 4.3.3 I have this question...

 

If I have the following code in my catalog/includes/header.php file does that indicate that a previous version of STS is installed?

 

// STS: ADD

$sts_block_name = 'applicationtop2header';

require(STS_RESTART_CAPTURE);

// STS: EOADD

 

Thanks,

 

Mike

Yes, Mike. It appears you have a version prior to version 4. You will have to uninstall the previous version before you can upgrade to STSv4 or above.

[bkellum]

LOL - well, now that I've asked the question I think I've found the answer :blush:

 

I changed the above link to this:

<a href="java script:history.back(1)"><?php echo tep_image_button('button_continue.gif', IMAGE_BUTTON_CONTINUE); ?></a>

 

It appears to be working the way I wanted it to, and it does not seem to be losing the Session ID - YAY! Do you see anything in the above link that you know causes problems?

 

PS - the forum seems to want to separate javascript into two words when I post this - it's only one word in my link

This is what I use and it is very similar to what you came up with:

<A HREF="java script:history.back()"><?php echo tep_image_button('button_back.gif', IMAGE_BUTTON_BACK); ?></a>

So, in the above, I use the back() function which will take the browser back to where it came and you used the back(1) which does the same thing. I also changed the button to a back button but a continue works as well. ;)

[m45537]

Yes, Mike. It appears you have a version prior to version 4. You will have to uninstall the previous version before you can upgrade to STSv4 or above.

 

 

Bill,

 

Thanks!

 

Now I have to ask, how do I uninstall a previous version without crashing my site?

 

I also have a question with regards to setting up a couple of sites, is this the best place to post it?

 

Thanks,

 

Mike

[bkellum]

Bill,

 

Thanks!

 

Now I have to ask, how do I uninstall a previous version without crashing my site?

 

I also have a question with regards to setting up a couple of sites, is this the best place to post it?

 

Thanks,

 

Mike

Mike, Make a backup of your application, files and database. You will need to remove the STS code from your previous installation from the following files:

• application_bottom.php
  
• application_top.php
  
• column_left.php
  
• column_right.php
  
• configure.php
  
• footer.php
  
• header.php

Now delete the following files from your shop:

• sts_display_output.php
  
• sts_product_info.php
  
• sts_restart_capture.php
  
• sts_start_capture.php
  
• sts_stop_capture.php
  
• **sts_user_code.php

Before you delete the sts_user_code.php file, save any custom tags you may have created so that you can add them to your new sts_user_code.php file in STSv4.4 using the new syntax format as you will see in the new sts_user_code.php.

 

Hope this helps,