Jump to content

Rigadin

Members
  • Content count

    138
  • Joined

  • Last visited

Everything posted by Rigadin

  1. Rigadin

    [contribution] STS PLUS v4

    Hi, If you are using STS PLUS v4 (which is a different contribution than STS v2 or v3), you don't need to do any change in configure.php and your shop will not look different after installation because the contribution is off by default. Please tell what version you are using. - Rigadin
  2. Rigadin

    [contribution] STS PLUS v4

    How to add infoboxes in sts_user_code.php: there is a problem in the example, so it won't work correctly. The correct code should be: $sts->start_capture(); require(DIR_WS_BOXES . 'new_thing_box.php'); $sts->stop_capture('newthingbox', 'box'); // If $sts->stop_capture('newthingbox', 'box') is followed by $sts->start_capture, you can replace both by $sts->restart_capture('newthingbox', 'box') Sorry for this one, it will be corrected in the next version... - Rigadin
  3. Rigadin

    [contribution] STS PLUS v4

    STS PLUS is a bit different than STS for the management of product_info templates. 2 ways to make it work: 1) STS PLUS way: you have a main template in sts_templates/test/ folder with the placeholder $content, and a content template in the folder sts_templates/test/content/ which contains your $productname$ and other placeholders, but without header/columns/footer. The content template will replace $content on the main template. You can name your content template product_info.php.html and it will be used for all products. Look chapter 3.9.1 and 3.9.2 of the doc (v4.0.5) to see how the templates are chosen according to product and category ID. 2) STS way: since STS PLUS v4.0.5 you can enable a "compatibility" mode in the product info module that will allow you to create a sts_template/test/product_info.php.html template with $productname$ in it. Depending on how you want to design your shop, the 1st method can save you design time as well as parse time. NOTE: if you use content template, you have to put <?php DEFINE ('STS_CONTENT_END_CHAR', '$'); ?> in your template if you want to use a '$' at the end of the placeholders.
  4. Rigadin

    [contribution] Simple Template System (sts)

    About adding a login box: if $loginbox does not work, try to create a $login_box. I've read somewhere that $loginbox was not working, but I don't remember why. - Rigadin
  5. Rigadin

    [contribution] STS PLUS v4

    New version 4.0.5 is available on the contribution page. The changes are: - Corrected $templatedir and $templatepath, they were always empty. - Added possibility to create templates for the manufacturer page. - Better compatibility with templates created with STS v2 or v3 (so far I have not found incompatibilities) To Andreas2003, about infoboxes: - Infobox Skin Manager (ISM) is using a slightly modified version of the class "boxes", I don't think that the code itself slows down the site. Perhaps the jpg files created by this contribution are too big and can influence when loading the first page. - I have never used Infobox Customizer, but it looks like everything is like in base osC except that you can give own CSS style and corner images to each box, so it will still be painful to add shadow effect for example, and not faster than ISM. - Anyway, one day STS PLUS will have html templating for infoboxes. It is already working in beta version, - Rigadin
  6. Rigadin

    [contribution] STS PLUS v4

    - STS and STS PLUS are used to easily change the place of the elements by designing templates. You can change the place where a box is displayed, but you can't change the design of the box itself. To change the infobox design, like adding a shadow, the best is the Infobox Skin Manager. - Except for the product info page, you can't change the main content of the page. - For Ultra Image, no problem as long as you don't use a product info template. If you do, you have to create a new template variable with the Ultra Image code in it, and place this variable on your template. There is an example on how to it in the file sts_user_code.php. I hope it helps. - Rigadin
  7. Rigadin

    [contribution] STS PLUS v4

    If you have followed the install instruction of Wolfen Feature set, the newproduct box is replaced by the featured products box of Wolfen. So the question is: do you see the Wolfen featured products? As mentioned earlier, there should be no problem with this contribution as it involves only the content of index.php - Rigadin
  8. Rigadin

    [contribution] STS PLUS v4

    I have never used Wolfen Featured Set, but it seems that this contribution modifies only the content of index.php, so there should be nothing to do to make it work. Please tell me if you make it work it or not, I'm interested in this contribution. - Rigadin
  9. Rigadin

    [contribution] STS PLUS v4

    If you are not using $urlcat_* variables, it should be okay. There are STS users who are also using Ultimate URLs. The problem with $urlcat is that these variables were buggy when I tried them, so they are not (yet) in STS PLUS. - Rigadin
  10. Rigadin

    [contribution] STS PLUS v4

    For now the product listing is like in sts v2/v3 and osCommerce in general: it is hardcoded. However, I have also this feature in mind and have an idea how it could work using an html template. Just need time or somebody with more time than me... For an easy way to change the infobox skins, I recommend Infoboxes Skin Manager, you can find it here: http://www.oscommerce.com/community/contributions,1680 - Rigadin net
  11. Rigadin

    [contribution] STS PLUS v4

    I don't know how (maybe my fault?) but 2 modules were buggy. I just placed an update on the contribution page. Note: if you use only index.php.html and not any template for some specific category (like index.php_1.html), you do not need to install (in admin) the module for index.php pages, the default module is enough and faster. - Rigadin
  12. Modules v1.1 are not compatible with v2.0, it means that you need to change your modules when you make the upgrade. I'll release v2.0 modules shortly. The SQL file provided with v1.1 is for the HtmlArea editor and you do not need to remove anything from database when upgrading to ACA 2.0
  13. Rigadin

    [contribution] STS PLUS v4

    The upgrade is quite simple: remove STS 3 and install STS PLUS. The list of files modified is not long and the modifications are easy. I don't see any problem with that. For the compatibility, there are few things that have to be checked: - Javascript scripts: in STS 3 there is a separate file, while STS PLUS uses the method of STS 2. I have not seen any problem but it can be, with some contributions. - $footer, in STS PLUS, includes only the copyright information while in STS it includes a full html table with counter, copyright and date. - $banner, in STS PLUS, includes only the banner while in STS it includes a full html table. - The way to proceed with product info templates (like product_info.php_26.html) is a bit different as it is now possible to create templates only for the content part of the page, while header, columns and footer are coming from the category template. It is however possible to make it work like in STS 3, I'll have a look on that and write instructions on how to do it. If you are using $footer and/or $banner, you can modify the file includes/modules/sts_inc/sts_footer.php to be compatible with STS 3. I'll do it in the next version, as I would like to reach a high compatibility level. - Rigadin
  14. I have made a version 2.0 of this helpful contribution, it is available here: http://www.oscommerce.com/community/contributions,2611 Here are the changes from v1.1 to v2.0: - Added modules management to the admin panel, no need to modify categories.php to use them. - categories.php much more similar to the original file, making much much easier to install contributions "the old way" (for contributions that does not have an ACA module yet) - modules of v1.1 are not compatible with modules of v2.0 - Installation instruction provided - Rigadin
  15. Rigadin

    [contribution] Simple Template System (sts)

    Sorry, I read quite fast these topics. Do you have a configure.php file in the folder includes/local ? If it exists, you should also add the definitions there. - Rigadin
  16. Rigadin

    [contribution] STS PLUS v4

    You can find STS PLUS contribution here: http://www.oscommerce.com/community/contributions,3893 If you need support for the original STS contribution, you should go there: http://forums.oscommerce.com/index.php?showtopic=58541
  17. Rigadin

    [contribution] Simple Template System (sts)

    Hi, Looks like some definitions are missing from your configure.php file. Look at the end of the file configure-SAMPLE.php delivered with the STS contribution, there are few lines that need to be copied into your configure.php (in the catalog/includes/ folder). - Rigadin
  18. Rigadin

    [contribution] Simple Template System (sts)

    Hi, STS does not modify the style of the product listing, so if you want to modify the look of your listing, you have to modify index.php and/or the module product_listing.php. There are some contributions doing that. - Rigadin
  19. Rigadin

    [contribution] Simple Template System (sts)

    Look in column_left.php how the other infobox tags are created. You have to create your own $myloginbox in the same way and then use $myloginbox in your template. - Rigadin
  20. The categories and products modules are not included with this ACA contribution but with their respective contribution. If a contribution you want to install includes an ACA module, then you don't need to modify categories.php but just install the module. - Rigadin, osc-help.net
  21. Rigadin

    [contribution] Simple Template System (sts)

    I meant: http://www.oscommerce.com/community/contributions,207
  22. Rigadin

    [contribution] Simple Template System (sts)

    STS supports Header Tags Controller, contribution 207. - Rigadin
  23. Rigadin

    [contribution] Simple Template System (sts)

    You can create a template named contact_us.php.html that will be used for the contact_us.php page. You can change header/columns/footer like you want, but the center of the page ($content) will still be the same. If you want to change the center too, then have a look on how it is done with product_info.php. - Rigadin
  24. This contribution removes the pain of modifying the admin/categories.php when installing new contributions. The logic is put inside separate modules instead of inside a 1500 lines long code. The problem with ACA is that it is difficult to install contribution "the old way" if no module exists and it can also be difficult to make a module... v2.0 is on dev, it will be a contribution to install over the original categories.php and modules will be setup like a shipping module => the "old way" installation can still be done and adding modules will be even easier.
  25. Rigadin

    separate pricing 411

    Do you mean that you want to set different prices per quantity ordered per group of customer? If yes, look at contribution 3039 (Quantity Price Breaks for Separate Pricing Per Customer)
×