Jump to content

Rigadin

Members
  • Content count

    138
  • Joined

  • Last visited

Everything posted by Rigadin

  1. Rigadin

    [contribution] STS PLUS v4

    With STS PLUS the layout of your pages are made in an html template, so you fix the width of your store by editing this template with your preferred html editor. Easy. The other good point is that STS PLUS does not modify many php files. With BTS the logic code (db queries, ...) is separated from the layout code, but you still have to edit php files if you want to change the layout. So basically it is same as with stock osC. If you use BTS, you also have to modify all files in catalog folder, which makes install of other contributions more tricky as there is less support. Anyway, I think I'm not the best person to compare as I'm much involved in STS PLUS and I like it! I've seen some other posts where people compare the solutions, maybe you can have a look there too. - Rigadin
  2. Rigadin

    [contribution] STS PLUS v4

    I guess the problem is this one: - In your template you include the stylesheet like that: <link rel="stylesheet" type="text/css" href="stylesheet.css"> So when editing your template, the stylesheet in use is catalog/includes/sts_templates/YourFolder/stylesheet.css but when viewing pages, the stylesheet will be catalog/stylesheet.css - You have changed the link to the css file on your index template, but not on the default template => only categories are ok now. Solutions: 1) You can use an absolute link http://www......../stylesheet.css 2) You can put the css file in the same folder as your template and use the $templatedir or $templatepath (they are same) to tell where is your sts_templates dir, example: <link rel="stylesheet" type="text/css" href="$templatepath/stylesheet.css"> 3) For development, you can have a copy of your stylesheet in 2 folders (catalog + same as your template), so it allows to edit the template as well as see store pages correctly, then later change to solution 1 or 2. Note that you have same problem with images when using relative links. - Rigadin
  3. Rigadin

    [contribution] STS PLUS v4

    If it works without STS PLUS... then there is a problem with STS PLUS. But what? The language of the date and time is set in the language file (english.php, dutch.php) with the call of the @setlocale function. After this call, the server knows how to display date and time. STS PLUS does not use this function and build the $date variable after the call of this function. Try to copy the line with setlocale from your dutch.php to the beginning of application_top.php and tell me the result. When searching for this, I found another difference: STS and STS PLUS do not put the constant HTML_PARAMS inside the <html> tag in page header. The writing direction as well as language of the page is defined in this constant and it can be useful for indexing in search engines. Patch coming soon.. - Rigadin
  4. Rigadin

    Bundled products

    There is a problem in javascript that goes in admin/categories.php, in the function fillCodes( ), the line var name = document.new_product.subproduct_selector[document.new_product.subproduct_selector.selectedIndex].name should have .text at the end, not .name I've seen this problem in Firefox but not in IE. Now it works in both. - Rigadin
  5. It could be done on the admin side, when adding a product, so no problem with the parse time of the page. - Rigadin
  6. Rigadin

    [contribution] STS PLUS v4

    The both texts you are searching for are in the language file of product_info.php, located here: \catalog\includes\languages\english\product_info.php They are in the original 2.2MS2 and STS PLUS does not modify them. - Rigadin
  7. Rigadin

    [contribution] STS PLUS v4

    Looks like your file includes/boxes/info_pages.php does not exist. Verify the name. Are you using Infobox Skin Manager? - Rigadin
  8. Rigadin

    [contribution] STS PLUS v4

    If I remember correctly, your contribution adds an infobox in one of the columns, and from this box you have links to extra pages that will display in the middle of the page. To add an infobox with STS PLUS, look in the file sts_user_code.php, there is an example. You have to choose a variable's name for your box, like 'extrapagesbox' and you can then use the placeholder $extrapagesbox on your templates. There should be nothing to do for the content part. Thanks for the compliments, Rigadin
  9. So far the latest version of ACA is v2.2 and you should make the update if you are running v2.0 or v2.1 . Here is the list of available modules for ACA2 (the contribution nbr is in brackets): [0716] Separate Pricing Per Customer 4 (SPPC) [1347] Htmlarea 1.7 JS for products modules [1347] Htmlarea 1.7 Editor for products description [1347] Jpsy uploader for product image [1347] Htmlarea 1.7 JS for categories modules [1347] Jpsy uploader for category image [1373] Category Description module [1373] Htmlarea for Category Description [1373] TinyMCE for Category Description [3039] Quantity Price Break for SPPC [3768] TinyMCE for product description Coming soon... [0207] Header Tags Controller (product + categories)
  10. - ACA v2.2 is out, make the update first. - HtmlArea and Jpsy work only in Internet Explorer. Which browser are you using? - If you don't use Category Description contribution, you do not need to install the 'Htmlarea 1.7 Wysywyg Editor for category description' module. There is no description available for categories in the stock osC, so no Wysiwyg editor. - TinyMCE editor is working in all major browsers, you can try it too. - If you are using IE and no Htmlarea, look in the html source of your page what are the javascript scripts added in header? - RIgadin
  11. Rigadin

    [contribution] STS PLUS v4

    I've just tried with default, index and product info modules without problem. The error you have is because you have modified index.php (and probably other pages in catalog too) to include header_tags.php, and now STS PLUS includes it again. Solution: remove the include of header_tags.php from each file in catalog, or add a condition for it: if ($sts->display_template_output==false) { ... If you add the condition, you'll still have Header Tags Controller working when STS PLUS is turned off. - Rigadin
  12. Rigadin

    [contribution] Simple Template System (sts)

    I'm not a user of CSS layouts, but I'm wondering how it works together with tables? STS adds a lot of tables, like in $contents for example. When I have this kind of problem, I save the result of the page to an html file and use this file in my editor to figure out where is the problem. - Rigadin
  13. There is a bug when inserting a new category. The right code, near line 79, should be: // ACA START INSERT CATEGORY TABLE $categories_modules->load_post_values ($HTTP_POST_VARS); $categories_modules->get_insert_table_categories($sql_data_array); // ACA END INSERT CATEGORY TABLE My EasyPhp did not give any error, strange... You do not need ACA2 to install SPPC, you can also make all the needed modifications manually in categories.php, like explained in the install instructions of SPPC. There is an ACA module for Head Tags, but is is for ACA v1.1, not 2.0. The module for ACA2 is not yet released. I have it working for products but not yet for categories. I'll release the product module soon. You can also add it again directly into categories.php, better use a file compare program in this case. Not yet. And I'm not sure I'm going to do it as I'm not sure I need this contribution. - Rigadin
  14. Rigadin

    [contribution] STS PLUS v4

    If you are using Header Tags Controller (contribution 207), get the STS PLUS module from there and follow the instructions. If you are using another contribution, look anyway at this module to see how it works. Why HTC does not work: this contribution adds text in the header of the page, between <head> and </head>, but STS does not care of it as it takes the header from the html template. How it works in STS PLUS: The STS variable $headertags ($sts->template['headertags'] in the code) contains by default the TITLE meta tag (like in standard osC) and it will be automatically added to the header of your html templates (no need to put it yourself). You can now add code in sts_user_code.php, or create a module like the one for HTC, to overwrite or modify this variable like you want. It will be automatically displayed on your pages. Note 1: as mentionned, you do not need to place $headertags on your template, but the <!--$headcontent--> is needed! See template examples delivered with the contribution. Note 2: you do not need to modify all files in the catalog to call the HTC file, as STS PLUS will ignore the result! I would be proud if you choose osCommerce because of STS PLUS! It seems that you have missed something during installation, because at least one file is missing. Take the last release 4.0.6, copy the files from the 'upload' folder to your application, if you have a fresh install od osC you can also copy the files from the 'clean_osc' folder. Then you should see the 3 STS PLUS modules in your admin panel. It is declared in includes/modules/sts_inc/general.php. Find the line: $sts->template['cataloglogo'] = '<a href="' . tep_href_link(FILENAME_DEFAULT) . '">' . tep_image(DIR_WS_IMAGES . 'oscommerce.gif', 'osCommerce') . '</a>'; Quite stupid piece of code, text should come from a language file! In fact it is same as in stock osC. One way is to modify this tag, the other way is to not use $cataloglogo on your template but place the logo yourself. Ouch, long reply, need coffee... - Rigadin
  15. Rigadin

    [contribution] Simple Template System (sts)

    If you are using the "Down for Maintenance" contribution which allows to disable the left and right columns when in maintenance mode, you must enable them. If you don't want to see these columns, create a template without, only for this contribution. - Rigadin
  16. The right code should be: // ACA START CATEGORY EDIT $categories_modules->display_edit($contents); // Display modules content // ACA END CATEGORY EDIT I'll release a new version with corrected bug. - Rigadin
  17. Rigadin

    [contribution] STS PLUS v4

    $footer and $banner are still existing, but not by default, here is the history: STS PLUS v4.0.4 $footer contains only the copyright text and $banner contains only the banner, no html table. It means that they are different than in STS v2/v3. STS PLUS v4.05 $footer becomes $footer_text and $banner becomes $banner_only. I changed the names because these variables are different than in STS v2/v3. $footer (with date, copyright text and counter in an html table) and $banner (banner in an html table), like the original ones, are now available in sts_user_code.php but they are commented out. Uncomment them if you prefer using them. I prefer the new ones because no html table and no counter, it gives more flexibility to design the template. I made these changes to keep the compatibility with templates made with STS v2/v3 NOTE: since v4.0.5 you also have $cat_ and $urlcat_ as comment in sts_user_code.php, but it is not recommended to use as it is quite slow. - Rigadin
  18. Rigadin

    [contribution] STS PLUS v4

    Hi everybody, I have added a new revision 4.0.6 on the contribution page. Changelog is: - BUG corrected in class sts.php: module was always sorting the big array of templates variables. Now should be faster when using an end-char for placeholders like $categorybox$. - UPDATED example in sts_user_code.php as it was not working. Sorry. - ADDED 2 new variables for product_info templates: $productid and $productsid, both contain the product ID. These 2 variables were existing in STS v3. - ADDED new variable for product info templates: $alsopurchased to display the box with items also purchased. - Rigadin
  19. Rigadin

    [contribution] STS PLUS v4

    Those texts are defined in the language file of product info page, located here for english: catalog/includes/languages/english/product_info.php They must be there, check the original osc 2.2MS2 file. - Rigadin
  20. Rigadin

    [contribution] STS PLUS v4

    Hi, Here are the answers: 1. When using a product info template, the display of the options is created in the file includes/modules/sts_inc/product_info.php about line 79. The code looks like that: $template_pinfo['optionnames'] .= $products_options_name['products_options_name'] . ':<br>'; $template_pinfo['optionchoices'] .= tep_draw_pull_down_menu('id[' . $products_options_name['products_options_id'] . ']', $products_options_array, $selected_attribute) . "<br>"; Try to add a second <br> at the end of both variables. 2. The product ID is not sent to the popup window because the placeholder $productsid you are using in the link does not have a variable associated. No need to correct this now, see next point. 3. You have to create the php code to build the links for "Larger Image | Back Image | Detail" and put it in a variable, then use the corresponding placecholder on your template. You can place the code in sts_user_code.php but it will then be called for each page, so it is maybe better to put it at the end of includes/modules/sts_inc/product_info.php. It should look like that: $mystring=[your code to build the link string here (the php variable $products_id contains the product ID)]; $template_pinfo['myimageslinks']=$mystring; You can then use $myimageslinks where you want on your product info template. - Rigadin
  21. Rigadin

    [contribution] Simple Template System (sts)

    In both STS and STS PLUS, the idea is to send the html code to a buffer instead of to the browser. This buffer is an array which many elements, each representing a part of the page. At the end, a piece of code replace the placeholders of your template by the corresponding element of the buffer. The $content is the piece of html generated between the end of column_left.php and the beginning of column.right. Look at these 2 files to get the idea. In STS, the output you see in your browser is generated by a file named sts_display_output, much of the magic things happened here.
  22. Rigadin

    [contribution] STS PLUS v4

    Hi all, If you are using Header Tags Controller contribution, you can download the corresponding STS PLUS module from the contrib page here: http://www.oscommerce.com/community/contributions,207 Installation is quite simple: copy the file to the right place and configure your modules to use this file. Instructions are included in the contribution.
  23. Rigadin

    [contribution] Simple Template System (sts)

    Hi, The forum support for STS PLUS is here: http://forums.oscommerce.com/index.php?showtopic=187122 Anyway, both STS and STS PLUS works same: The $content is the result of the php code of your script, like for a shop without STS. If you want to change how the content looks like, you have to modify the php code, for example index.php. For product_info.php, you can create templates where you can place each element where you want (image, price, description, ...). With STS PLUS, you can code modules that will handle the content of each page in the same way as product_info.php, but first you should be little bit familiar with the system.
  24. Rigadin

    [contribution] Simple Template System (sts)

    Check in configure.php where is defined the STS_TEMPLATE_DIR constant. Your product_info template is in folder includes/sts_templates/ and probably STS_TEMPLATE_DIR is not set to this folder.
  25. Rigadin

    [contribution] Simple Template System (sts)

    Your site is always using the default template includes/sts_template.html, quite strange if on your local machine it takes the product_info.php.html. Have you done the update from Christophe B. on 25 aug 2004?
×