Jump to content

Rigadin

Members
  • Content count

    138
  • Joined

  • Last visited

2 Followers

Profile Information

  • Real Name
    Chris
  • Location
    Lausanne, Helsinki, St-Petersburg
  1. Rigadin

    [contribution] STS PLUS v4

    Terve Tero, You should have only sts_user_code.php in the parameter 'files for normal template'. The files sts_column_left.php and sts_column_right are already called respectively in includes/column_left.php and includes/column_right.php. If you add them in 'files for normal template', the code for the infoboxes will be processed twice and the main content will disappear or be strange. You can skin your infoboxes with this contribution: http://www.oscommerce.com/community/contributions,1680 or wait a while that STS can do it (it's in dev). To all of you who change the default template and do not see the result in your store: leave only sts_template.html in your template folder, remove the other templates. You can add them later when you are more familiar with STS PLUS.
  2. Rigadin

    [contribution] STS PLUS v4

    Try to place whatever text in you variable: $template_pinfo['relatedbox'] = 'Hello World' and check is it coming or not on the page. Is there any logic inside the code of the box that could prevent it from displaying? Run in debug mode and check for the content of the 'relatedbox' variable, is it empty or not?
  3. Rigadin

    [contribution] Simple Template System (sts)

    Do you mean that you want a category box that does not display the top level categories? That needs a hack of the categories.php box and has nothing to do with STS. Probably someone has done it already, search the forum. If you want that the only expanded category is the selected one, well, this is the stock osC behavior. by default the categories not selected are collapsed. Try the original categories.php box if it fits your needs, but once again, content of boxes is not modified by STS. - Rigadin
  4. Rigadin

    [contribution] STS PLUS v4

    So if I understand correctly, the relatedbox goes under the content, like the also purchased box. Based on that, I see 2 choices: 1) place $relatedbox on your content template. 2) As $relatedbox is already created in sts_column_left, make it available in content template by placing $template_pinfo['relatedbox']= $sts->template['relatedbox']; inside the file includes/modules/sts_inc/product_info.php
  5. The extra fields are located in another DB table, so Easy populate won't find them, so they won't be in your CSV. I have not seen any ready solution for that, you should check the Easy Populate forum thread: http://forums.oscommerce.com/index.php?showtopic=162244
  6. Sorry I'm also out of topic, but this is a general tip for all CCGV users and osCommerce users in general: Use a file compare program to make your changes! On one side you have the 'clean' osC files delivered with the contribution and on the other side you have your shop. You can see the differences and make the necessary updates line by line if needed. I can't think working without this kind of tool. I'm using Beyond Compare from Scooter Software and it's great. - Rigadin
  7. Rigadin

    [contribution] STS PLUS v4

    If the infobox goes into a left or right column, then it has nothing to do with the content template. When you use a content template for your product_info.php page, another template is used for header, columns and footer (use the debug mode to see the path to this 'outside' template) and probably your infobox is missing on this one. If the place of your infobox is under the content, then do like this (in the 'outside' template): $content $relatedbox so $content will be replaced by the content template and $relatedbox by your infobox. - Rigadin
  8. For HTC users: The HTC contribution must be installed completely, except the modifications to categories.php. If meta tags do not show up in your pages, be sure that the values you enter in the product or category editor are saved in the database (are these values back when you edit again this product/category?). If this part is ok, put this line in the file includes/header_tags.php: die(); If your page is blank, the file is correctly processed and refer to the HTC support forum for... support. If your page still shows up normally, you have not made the correct modifications in your catalog scripts (for non-STS PLUS users) or you have set something wrong in your STS PLUS modules (for STS PLUS users of course). For Htmlarea users: To make the ACA modules for htmlarea, I have used the version found in this contribution: http://www.oscommerce.com/community/contributions,1347. You should have a look at TinyMCE for a cross-browser Wysiwyg editor! For Products Extra Fields users: There is now an ACA2 module for this contribution, available on its download page. There is also a new version of ACA, version 2.4, needed when using Products Extra Fields. - Rigadin
  9. Rigadin

    [contribution] Simple Template System (sts)

    Two choices - Create the link using osC functions, put it in an STS variable and place the corresponding placeholder on your template, this is the only way to get the osCsid to follow your customer from page to page. - Force the use of cookies (parameter in admin). The osCsid is not needed anymore. This is also more friendly for search engines and more secure. I'm not doing any store without forcing the use of cookies. If customers are not ready to accept cookies, for sure they are not ready to buy from internet! - Rigadin
  10. You have to take HtmlArea folder from contribution ID 1347 instead of ID 2512. There are some differences concerning the insert image URL function. - Rigadin
  11. Rigadin

    [contribution] STS PLUS v4

    Have you installed some kind of infobox manager? The box should be created using the following code (in product_notifications.php): new infoBox($info_box_contents); but in you case there is 'infoboxdefault' instead of 'infoBox'. - Rigadin
  12. For now there is no ACA2 module for Products Extra Fields contribution and using the old module will give an error. I'll need this module one day but can't give any timetable when I'll do it. - Rigadin
  13. You need to have <!--$headcontent--> in the <head> section of your template. You have installed the HTC ACA module, but you still need to install HTC on the catalog side: there is a file named header_tags.php in the catalog/include/ folder and also one file in each language folder. - Rigadin
  14. Rigadin

    [contribution] STS PLUS v4

    To Mark: SPPC is not a problem. Try to run STS PLUS in debug mode (add sts_debug=debug in URL) and you will see some more informations, like which template is being used and what code is in the placeholders. Check if the path to the template is correct. To qubertman: There are some boxes that change depending if customer is logged in or if there is a product displayed. This is the behaviour of "old" STS and it is still same with STS PLUS for compatibility reasons. However, with STS PLUS you also have a placeholder for each infobox separately, so if you use both, you will sometimes see two times the same box. Check the doc, there is a complete list of placeholders with their meaning. - Rigadin
  15. Rigadin

    [contribution] STS PLUS v4

    Do you mean how to change the skin of the infoboxes that display in the content area? Well, you have to find where they are build and change a function call. Example with includes/modules/new_products.php: near the end, call the function like this: new contentBox($info_box_contents, true, 1); Which will skin the box with skin number 1.
×