Jump to content

Rigadin

Members
  • Content count

    138
  • Joined

  • Last visited

Everything posted by Rigadin

  1. STS PLUS is a variation of the famous and excellent STS (Simple Template System) created by Brian Gallagher. The goal is the same: use an html template to modify the look of the shop. How STS and STS PLUS work: Instead of displaying the result of the scripts straight to the browser, STS "captures" it into variables. To each variable corresponds a placeholder (for example "$banner") that can be placed on an html template. STS will then replace all placeholders with the corresponding code and display it in the browser. This involves only few modifications of the osCommerce files while allowing changing the design of the shop by modifying an html page. In its most simple form, only one template is created and it will be used for all pages of the shop. It is also possible to create a template for a specific page, a specific category or a specific product. There were few things I wanted to do better in the STS contribution and it ended up in a quite different structure and code, so I made a new contribution. However, "old" templates can still be used. Main changes: - Group the templates in sets and select the displayed set from admin panel. - Test a set of templates only for admin: test your new templates online without disturbing your visitors. - Turn STS PLUS on/off from admin. If turned off, the normal osC will be displayed. - Turn STS PLUS on only for admin: test your templates online without disturbing your visitors. - Less html in placeholders, so more flexibility for the design work. - Code specific to a page is put into a module. Advantages: use only modules you need => less code processed. Write your own module to integrate a contribution and share the modules with other users. - Module are configurable from admin panel, like you do with shipping modules. - Less code, should be faster. - For the product info page, possibility to have a template only for the content area, while header, columns and footer are coming from the category template. - All boxes are available separately, no need to show specials if you want to show tell a friend box, no need to show best sellers if you want to show product notifications. - Possibility to place php scripts in the templates (like in STS v3). Installation of this contribution is very easy. Please read the doc available with the contribution, I have write quite much there. I will post the link to the contribution after I have add it to the contribution section. Have to start somewhere...
  2. 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.
  3. 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?
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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.
  17. Rigadin

    [contribution] STS PLUS v4

    Infobox Skin Manager works very well with STS PLUS, and it helps a lot customizing your infoboxes! You should not install the whole contribution, as it has some options to skin also columns, header and footer (and you'll do this with STS PLUS). So, as far as I remember, you should follow the install instructions BUT DO NOT make any modification in header, column_left, column_right nor footer.php . By the way, I tried your site with DHTML menu but no way to see anything, only transferring stuffs but nothing came my screen. For this menu, there is a part to put just after the <body> tag, I told yesterday that have to modify all files in catalog... I don't know why I said so as this is something you can typically do with STS PLUS: create new variable with the code inside and place it on your template, like every other variable. - Rigadin
  18. When installing HTC, have you made any modification to the catalog side? There are some new files that need to be there. As you are using STS PLUS, you do not need to modify all files in catalog an extra file. In your template, do you have the $headcontent placeholder in the header? Without this you'll not have the meta tags.
  19. Rigadin

    [contribution] STS PLUS v4

    DHTML menu: - For the 1st modification required after the <body> tag, I don't see any other way than modifying all files in catalog. Try with one file first, to see if the menu working. - For the 2nd modification required inside the <head> tags, you can put it directly inside the template instead than in the sts class. - The 3rd modification must be made in sts_column_left.php
  20. If you can see the meta tags in the product editor and save them, then the problem is in the catalog side. As you are using STS PLUS, have you copy the HTC file that is made for STS PLUS and have you configured the STS PLUS module(s) to use this file? - Rigadin
  21. Rigadin

    [contribution] STS PLUS v4

    Could you post the piece of code you did in sts_user_code? It should look like this: $sts->restart_capture ('notificationbox', 'box'); The 'box' parameter is important to remove some <tr><td> that are added to all boxes. Without this the layout is mixed. You can also run STS PLUS in debug mode and check if you custom boxes have extra html comparing to other boxes. - Rigadin
  22. Rigadin

    [contribution] STS PLUS v4

    If you have a clean osc installation, take the files from the 'clean_osc' folder AND from the 'upload' folder. If you don't have a clean osc installation, take files from the 'upload' folder only and make the other changes manually (best with a file compare program). - Rigadin
  23. Rigadin

    [contribution] STS PLUS v4

    Did you check with STS PLUS disabled? I have feeling that this is not STS PLUS problem. The infobox categories.php calls the function tep_has_category_subcategories, which has this type of query. Use the cache function for category box to reduce queries. - Rigadin
  24. Heiko, You probably have installed ACA correctly, but you don't have any module available in admin/includes/modules/categories or /products => you don't see anything from admin side. Modules are available with their respective contribution. - Rigadin
  25. Rigadin

    [contribution] STS PLUS v4

    You most probably made a mistake during installation of STS PLUS. This contribution does not interfere with Admin Access. - Rigadin
×