Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/14/2013 in all areas

  1. 11 points
    Hi All.. Here are instructions on how to check how compatible your online store installation / PHP code is against all PHP versions from 5.0 up to the latest version (currently 7.3). This guide requires a minimum PHP 5.4 version to run. This is a medium level skill guide and requires the installation of Composer - a dependency manager for PHP that manages the installation and updates of third party libraries. I will link to the installation instructions of Composer instead of writing how to install it here. It's possible to perform this guide either remotely on the web server in a ssh terminal, or locally on a backup copy of the PHP code. Step 1 - Install Composer Composer can be installed on Windows, Linux, Mac, and Unix. If you're installing on Linux, there may be a Linux distribution package that can be installed depending on your access privileges on the server, otherwise a manual installation is required. The manual installation can be performed locally in your home directory without special user permissions. Instructions for how to install Composer on Windows can be found here: https://getcomposer.org/doc/00-intro.md#installation-windows Instructions for how to install Composer on Linux, Mac, and Unix can be found here: https://getcomposer.org/doc/00-intro.md#installation-linux-unix-macos Step 2 - Create Composer Project File Composer needs to create a composer project file in the directory where your online store installation or PHP code resides. This will create two files that will be publicly accessible through the web server - this will not pose any security issues. The setup will also eventually create a "vendor" directory however Composer will be configured to place this in the "includes" directory to block public web server requests to the directory. Copy and paste the following to composer.json in the directory where your online store installation resides: { "config": { "vendor-dir": "includes/thirdparty/composer" }, "require-dev": { "squizlabs/php_codesniffer": "^3.4", "phpcompatibility/php-compatibility": "^9.2" } } Step 3 - Install PHP_CodeSniffer PHP_Codesniffer detects violations of defined rules in your code. There are several coding standard rule sets available to make sure each PHP file meets the coding standards. There is no rule set currently available for OSCOM v2.x - for v3 the PSR12 rule set is used. As there will be a lot of violations running this with a coding standard, we will instead run it to use only one rule set to check compatibility against the latest PHP version. We will also configure PHP_CodeSniffer to ignore certain violations which is already taken care of in the online store installation. Run the following command to install PHP_CodeSniffer: composer install After this installs PHP_CodeSniffer and the PHP Compatibility rule set, a PHP_CodeSniffer configuration file will be created to configure the rule set that should be used. Copy and paste the following to phpcs.xml in the directory where your online store installation resides: <?xml version="1.0"?> <ruleset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="PHP_CodeSniffer" xsi:noNamespaceSchemaLocation="phpcs.xsd"> <description>The coding standard for osCommerce.</description> <file>.</file> <exclude-pattern>*/includes/thirdparty/*$</exclude-pattern> <arg name="basepath" value="."/> <arg name="colors"/> <arg value="nps"/> <rule ref="PHPCompatibility"/> <config name="installed_paths" value="includes/thirdparty/composer/phpcompatibility/php-compatibility" /> </ruleset> Step 4 - Run PHP_CodeSniffer PHP_CodeSniffer can now be executed with the following command. It will automatically use the configuration file created in step 3: ./includes/thirdparty/composer/bin/phpcs which will produce the following output report: FILE: admin/includes/functions/compatibility.php --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- FOUND 15 ERRORS AFFECTING 12 LINES --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 32 | ERROR | Global variable '$HTTP_GET_VARS' is deprecated since PHP 5.3 and removed since PHP 5.4; Use $_GET instead (PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_get_varsDeprecatedRemoved) 33 | ERROR | Global variable '$HTTP_POST_VARS' is deprecated since PHP 5.3 and removed since PHP 5.4; Use $_POST instead (PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_post_varsDeprecatedRemoved) 34 | ERROR | Global variable '$HTTP_COOKIE_VARS' is deprecated since PHP 5.3 and removed since PHP 5.4; Use $_COOKIE instead | | (PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_cookie_varsDeprecatedRemoved) FILE: admin/includes/functions/database.php ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- FOUND 25 ERRORS AFFECTING 24 LINES ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 179 | ERROR | Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead (PHPCompatibility.Extensions.RemovedExtensions.mysql_DeprecatedRemoved) 181 | ERROR | Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead (PHPCompatibility.Extensions.RemovedExtensions.mysql_DeprecatedRemoved) 185 | ERROR | Extension 'mysql_' is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead (PHPCompatibility.Extensions.RemovedExtensions.mysql_DeprecatedRemoved) Here we can see which files violate a PHP Compatibility rule set, the line in the file where the violation occurs, the reason for the violation, and the actual rule set that was violated that we'll be using to ignore the false positive reports with. In the example output, it states that $HTTP_GET_VARS, $HTTP_POST_VARS, and $HTTP_COOKIE_VARS are deprecated since PHP 5.3 and are still used in your online store installation. This is a false positive as osCommerce Online Merchant already has its own implementation to work with or around it. In this case, the variables are safely defined in admin/includes/functions/compatibility.php and includes/functions/compatibility.php. It also states that "mysql_" is deprecated in PHP 5.5 and still used in the online store installation. This is also a false positive as osCommerce Online Merchant wraps calls to the "mysql_" functions if "mysqli" does not exist. We'll add to the PHP_CodeSniffer configuration the rules that can be ignored. The rules can be seen in the output report in brackets ( ). Below is an updated phpcs.xml file with a list of rules being safely ignored for a osCommerce Online Merchant v2.3.4.1 installation: <?xml version="1.0"?> <ruleset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="PHP_CodeSniffer" xsi:noNamespaceSchemaLocation="phpcs.xsd"> <description>The coding standard for osCommerce.</description> <file>.</file> <exclude-pattern>*/includes/thirdparty/*$</exclude-pattern> <arg name="basepath" value="."/> <arg name="colors"/> <arg value="nps"/> <rule ref="PHPCompatibility"/> <config name="installed_paths" value="includes/thirdparty/composer/phpcompatibility/php-compatibility" /> <rule ref="PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_get_varsDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_post_varsDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_cookie_varsDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_session_varsDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_server_varsDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_post_filesDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.Extensions.RemovedExtensions.mysql_DeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.IniDirectives.RemovedIniDirectives.session_bug_compat_42DeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.IniDirectives.RemovedIniDirectives.session_bug_compat_warnDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.FunctionUse.RemovedFunctions.session_registerDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.FunctionUse.RemovedFunctions.session_is_registeredDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.FunctionUse.RemovedFunctions.session_unregisterDeprecatedRemoved"> <severity>0</severity> </rule> <rule ref="PHPCompatibility.FunctionUse.RemovedFunctions.mysql_escape_stringDeprecatedRemoved"> <severity>0</severity> </rule> </ruleset> Please remember that a lot of false positives will be reported and will need to be individually checked to see if a workaround exists in the PHP code. Additional rules to ignore can be added to the PHP_CodeSniffer configuration file. Happy PHP 7.3 incompatibility hunting!
  2. 10 points
    piernas

    Shipping table is now a real table :)

    Today I decided I got angry for the last time updating a table rate based module. Afer several tryouts to change the shipping rates just to see I had a typo in the values string -damned colons- and having to manually calculate the net prices for each row from the gross that came from the table provided by the courier... I had enough and modified the table rate module to show a real table where you can see what you're doing. Uses some javascript to update net/gross, add or remove rows and do some basic checks. It can be adapted to any other module that uses the same system. Note: The net pice is caclulated based on the tax class from the module. It will apply only to the countries in the module's zone and it's not savet to database but calculated on the fly. For this column to work you need to set up the tax rate first, save and enter the module configuration again. Here is the file: https://apps.oscommerce.com/wyYLv&sgipping-table-module-update @burt you can replace the stock one if you consider it fits the community project.
  3. 9 points
    burt

    Bootstrap 4 in 2.3.4.1

    Code https://github.com/gburton/Responsive-osCommerce Demo https://template.me.uk/frozen2bs4/index.php Reminders Frozen is still frozen (at bootstrap v3) Admin is still not bootstrapped
  4. 8 points
    piernas

    Admin responsive sidebar with bootstrap

    This is a admin sidebar that replaces the stock menu. It can be expanded or condensed on a column of icons. It also adds bootstrap framework to admin. Hope you enjoy it. Please comment here if you have any improvements or find any problem. Download: https://apps.oscommerce.com/ebjVY&admin-responsive-sidebar-with-bootstrap
  5. 7 points
    burt

    Phoenix Announcements

    CE Phoenix CE Phoenix is a powerful ecommerce shop ready to use out of the box, putting you online and in full control of your business right from the start. Your customers will love the modern, responsive design that will not only make your website look great on all mobile viewing devices but also perform at speed whilst giving you the power to create an individual and unique look to your shop with just a few clicks! CE Phoenix is packed with many first class utilities as standard but its modular software design lets you add many more with no programming skills required. The full suite of product, shipping and payment options included will let you sell thousands of products in any number of categories worldwide in any currency or language providing a seamless customer experience. CE Phoenix is the official Community Version of osCommerce. Check out what you can do with CE Phoenix at the demo sites; Base Demo Supporters Demo https://template.me.uk/phoenix/index.php https://template.me.uk/supporters/index.php Support the Project If you or your employer is commercially dependent on Phoenix (or a previous incarnation), please help to sponsor continual forward movement in the code-base. Phoenix needs you as much as you need Phoenix! I am hopeful that all shopowners, developers, consultants and businesses will support the Project ... allowing two professional developers to work on the code on an ad-hoc basis. A Supporters subscription includes access to the current season of Supporters code as seen at the Supporters Demo shop. Join the Phoenix Club If you wish to help steer the future direction of the software please join the Phoenix Club https://forums.oscommerce.com/clubs/1-phoenix/ Thank You To all shopowners, developers, consultants and business owners who are supporting the Project. PHP Version Minimum Maximum 7.0 7.3 Image Credits Images in the default installation are copyright their respective owners; Image Owner Usage osCommerce Logo osCommerce https://www.oscommerce.com/Us&Legal#TrademarkPolicy Phoenix Logo G Burton Phoenix Logo may not be used without prior written permission from the copyright owner. Oranges, Lemons, Pears, Apples Eelffica from Pixabay https://pixabay.com/service/license/ Tomatoes Rocky_H from Pixabay https://pixabay.com/service/license/ Heart Gerhard Gellinger from Pixabay https://pixabay.com/service/license/
  6. 7 points
    Harald Ponce de Leon

    Naming Convention

    Yes, at Github. 1.0.0.0 to 1.0.0.2: https://github.com/gburton/Responsive-osCommerce/compare/v1.0.0.0...1.0.0.2 1.0.0.2 to 1.0.0.3: https://github.com/gburton/Responsive-osCommerce/compare/1.0.0.2...1.0.0.3 They will be made aware as CE releases use the same update mechanism from v2.3. This means the update procedure is manual for v2.3 based CE releases (the architecture does not support online updates). Automatic updates will first arrive with v3 and v3 based CE releases. Community Edition maintainers have the ability to push out a release to the website without my intervention. In fact, the website automatically checks Github once every hour to see if a new release has been pushed out at Github and automatically updates the download page and posts a news announcement if one was posted at Github. This will be addressed when Community Editions are officially announced. If they want to stay on PHP 5.6 they can with their current installation. If it runs perfectly today, it will run perfectly tomorrow, and there are active developers in the forum that can help when problems arise. If they want to move to another release or platform, they can't stay on PHP 5.6. There is a lot of excitement when releases are pushed out, however your current installation is not going to burn if you don't upgrade immediately.
  7. 7 points
    burt

    Bootstrap 4 in 2.3.4.1

    Bootstrap 3 will be around for years - no point overthinking that, so forget it. The main "problem" will be upgrade php. Some people say php7.2 is working fine, others report it is not working fine. At the end of the 28d, dependant on support thereof, I hope to have gotten enough time in hand to get the following done and complete; make sure shop and admin are ready for 7.2 (at the very least, possibly 7.3 if I can swing it) -> no warnings and no errors product class -> rework relevant modules to use it But as with all things, one step at a time, and right now that step is trying to get some time in hand to actually do "stuff".
  8. 7 points
    burt

    Product Page Layout

    Totally do-able, it is exactly as @raiwa says. Gallery 10 6 Name 20 6 Model 30 3 Price 40 3 Attributes 50 6 Buy 60 3 Reviews 70 3 Description 80 6 You are constrained by the DEPTH of the Gallery, so place a minimum height on this using CSS which would be placed in user.css @media only screen and (min-width : 768px) { div.cm-pi-gallery { min-height: 1000px; } } Change the min-height on this to better reflect your needs. You will then also need to amend tpl_ files for product_info, at the very least; remove clearfix from reviews button tpl restyle price as it would look weird as a h* Prior to the extra tpl_ change for price, you would end up with something like: Of course, how this would look in XS...is debatable, and that is why you can micromanage the layout using those tpl_ files if you so wish. My system for these modules uses only the SM layer.... however, that micro-management is where things get really complicated really quickly and hence why I did not put that level of management into Core.
  9. 6 points
    raiwa

    Slim Checkout for BS

    Slim-Checkout Common opinion is that the checkout process should be as "slim" as possible. This means to hide all page elements which are not strict necessary to show to the customer a simple clean layout, so nothing disturbs his attention from the purchase process. This add-on allows to do it by simple settings in a Header Tag module. Git Hub Repository: https://github.com/raiwa/Slim-Checkout/tree/master What it does: - allows to hide elements on checkout pages - optional hide on checkout pages (checkout_shipping.php, checkout_payment.phpheckout_confirmation.php and checkout_success) - optional hide also on shopping_cart.php - select each group to hide (navbar, header area, boxes, footer and footer suffix Installation: - copy all new files - install and adjust Slim Checkout Header Tag testing , Bug reports and suggestions very welcome. rgds Rainer
  10. 6 points
    Jack_mcs

    Category Images

    A new version has been uploaded with these changes: Added a version for Phoenix. Added an option to allow controlling which categories are displayed. Added a module for sub-categories. Added a module for categories with product pages. Changed install text to mention the equal heights addon. Corrected mistake in the module that was storing some of the settings in the wrong place. Corrected mistake in the css that would prevent other css from working. Moved the css code from user.css to the ext/css/category_images,css file. Replaced unused variable with the correct code. Found by member @Moxamint.
  11. 6 points
    I think it would be great to make a package (called frozen 2 or as you like) that has the new admin of @shetch and the Frozen version with its bug fixes so that new users can download them in one place. What the community lacks are periodic updates to show that the software is alive. I do not know if this is the best place to post it, but the work of @shetchis fantastic, it's the cooler in oscommerce for a long time and it would be great to integrate it into the Frozen package. What do you think? Best regards. Valqui
  12. 6 points
    burt

    Email queuing system

    Great, it's looking good... Burty signed up today but didn't complete a checkout - Email will go out in 5 days asking if there was a problem *** - Email will go out 31 July with birthday wishes (21 days prior to his birthday) Dan signed up today and gave his birthday, and completed a checkout - Email will go out 27 April wishing him a happy birthday (approx 3 weeks prior to birthday) - Email will go out 10th May (60 days) asking for a review - Email will go out 10th March 2020 asking why he hasn't ordered for a year *** Rene completed a checkout today - Email will go out 10th May (60 days) asking for a review - Email will go out 10th March 2020 asking why he hasn't ordered for a year *** Steve completed a checkout today - Email will go out 10th May (60 days) asking for a review - Email will go out 10th March 2020 asking why he hasn't ordered for a year *** *** - these emails get cancelled depending on customer interaction. As an example, let us say that Burty logs in 2 days from now (13 March)...and completes a checkout...what happens: no_checkout is cancelled as he has now checked out request_review goes out in 60 days (so May 12th or so) from the date of sale winback will go out about 13th March 2020 asking why he hasn't bought anything for a year (remembering that this would be cancelled if he did log in inside that year) Pretty cool little system ? I'm pleased with how it's turned out. You may have noticed I made a "no_checkout" slug - it took less than two minutes, no core code changes - all plugged into the system automatically. BOOM! That is the future of osCommerce.
  13. 6 points
    piernas

    Addon installer concept

    Now that oscommerce community version allows more an more addons with no core code changes I feel an uploader/installer would make things simpler and also help a lot those newcomers that does not have the knowledge to ftp files. We don't have a repository adapted to it, but we could ideate a simple system that allows to upload a zip file by browser, uncomprees it, do some preliminar checks like if the addon is currently installed and is compatible with the system and with copying files/making registry entries when user press "install". Been playing with the idea of something like the paypal app updater and came up with this: Would like to get feedback from developers about it. It would need, of course, that developers agree with packaging the addons with a certain structure and provide with a file that performs the tasks. Do you consider interesting to make a similar system?
  14. 6 points
    Addon is now available. Congratulations!
  15. 5 points
    Jack_mcs

    Information Pages SEO addon

    This addon allows the easy creation and handling of pages from within admin as well as a way to manage text on any page in the shop. It is based on the Information Pages Unlimited addon that has been around for years. While much of the code is different in this version, I wanted to keep the compatibility with the original version, thus the similar name. NOTE: There are three sets of files in this package, for different versions of oscommerce. The BS version is the only one that has all of the new features. The other two versions are improvements over the original code but nowhere near that which is in the BS version. So any instructions or descriptions may apply to the other versions but are mainly meant for the BS version. This version fixes many coding mistakes in the other version and adds many new features making it easier to use and more powerful. Some of the features are: - Has a Box ID setting that allows you to control where the link to the page shows up. So, for example, if there are four footer modules installed, each could have links specific to them. - A link can have sub-links (currently only available in the included module). So there could be a main link for widgets and sub-links for various kinds of widgets. There are two advantages to this: first, it takes up less room when there are many links and, second, the search engines will still be able to get to the pages.- There is a quick view button to allow displaying the page in a browser to check the changes. - There are quick fill options that allows categories and products to be added to a page with just a short statement. For example, if your site sells automobile parts and you are creating a new page about tires, you just need to type in PNAME(tires)PNAME and links for all of the products in your shop with tires in the name will be added to the page. See the Notes section on the editor page for additional methods. - Allows setting the browser title and meta tags while editing the page in admin (only if Header Tags SEO is installed).
  16. 5 points
    General support/feedback for Bootstrap 4 admin See https://apps.oscommerce.com/LCrov&amp;bootstrap-v4-oscommerce-admin-ce
  17. 5 points
    raiwa

    Store Logos Multi

    Store Logos Multi 1.0 Responsive and Localized Store Logos Store Logos Multi Compatibility: Responsive 2.3.4.1 BS CE Frozen and all 2.3.4.(1.) BS EDGE versions and GOLD PHP 5.4-7.2 How it Works: Responsive and Localized Store Logos will add a new Logo page to your admin where you can upload 3 different logo sizes for each of your store languages. A new alternative header content module is included which will display the Logo just like the standard core logo module. Purposes: 1. Serve different logo sizes to allow the visitors browser to select the most apropiate for it’s device size and resolution. The browser will automatically download only the logo which fits best it’s need. Example: You are using a banner style store logo which is set to half of the header width (col-6) - for a standard desktop screen and a retina tablet a width of about 640px would be good - for a retina desktop device with double resolution like i-mac, 1280px would be better - for a small simple mobile phone 320px would be optimum to save download time. This add-on allows you to upload 3 different sizes of your store logo (1280px, 640px and 320px for this example) If your store logo uses the full width (col-12), upload for example the sizes 2560px, 1280px and 640px. 2. If you wish to use different versions of the Store Logo for each of your store languages, you can now easy upload a different set of logos for each language. It is not mandatory, You can use one and the same logo and only upload to the default language. It will be used then for all languages.
  18. 5 points
    burt

    Phoenix Announcements

    1.0.0.4 hotfixes and enhancements How to update Make sure you have applied the 1.0.0.1 hotfixes -> 1.0.0.1.zip Make sure you have applied the 1.0.0.2 hotfixes -> 1.0.0.2.zip Make sure you have applied the 1.0.0.3 hotfixes -> 1.0.0.3.zip Apply the 1.0.0.4 hotfixes -> 1.0.0.4.zip You could also simply download & install the latest v1.0.0.4 https://github.com/gburton/Responsive-osCommerce/tree/1.0.0.4 and install it. You could make commit by commit changes 1.0.0.3 to 1.0.0.4: https://github.com/gburton/Responsive-osCommerce/compare/1.0.0.3...1.0.0.4 I suggest the simplest way (assuming you are on 1.0.0.3) is to grab the 1.0.0.4 zip, unzip it, and upload the files. Special Thanks @Harald Ponce de Leon for working on 7.3 compatibility 👍 the forum members who took time to look at demo site and point out issues 👍
  19. 5 points
    The next update will be pushed out this month and takes care of that 👍
  20. 5 points
    burt

    Bootstrap 4 in 2.3.4.1

    In addition to the multiple changes made to accommodate BSv4, I have also changed a few other bits; Content Module - Footer - Links Now easier to add in links Box Module - Information Ditto Breadcrumb Separate logic and display How are we finding the new osCommerce?
  21. 5 points
    raiwa

    Feedback for raiwa

    If you buy an addon you are buying software without instalation service. Each addon package includes instructions for instalation. However you’ve got free support through 20 mails including one free customization and advices for problems unrelated with the purchased add-ons. You have never engaged me any job and didn’t pay for any request.
  22. 5 points
    Tsimi

    ULTIMATE Seo Urls 5 - by FWR Media

    I just quote from google All what google says is they recommend or say it is good practice to make the URLs read-friendly so that customers/users can read or use the URL as link or navigation guide. It doesn't say one word that it will improve your SEO because of that. Google just says you should keep it organized. Another quote Again, no mention of SEO benefit. Visitor friendly does not equal better SEO or SEO results. Lastly, everyone can do what they want with their shop site it is their website and they should know what their customers might want. Look at Amazon, eBay or some other big shop they all have different URLs, some long, some short, some easier to read, some are super long and complicated. Important is that the "real" SEO stuff in your shop is working as it should then you'll end up getting good search results. So what @burt said isn't wrong at all. User friendly URLs have nothing to do with SEO.
  23. 5 points
    This addon minifies the shops css file. If multiple files are selected, it will combine them all into one file. This can reduce the time it takes for the shop to load. Depending upon the size of the css file and how many there are, the page load speed can be reduced by several seconds. It works in any oscommerce shop. For the 2.3.4 shops (both official and Responsive versions), the installation just involves uploading files. For older shops, one change may be needed.
  24. 5 points
    Tsimi

    Slim Checkout for BS

    @raiwa Well done! We appreciate all the hard work you put into your addons and projects but please do me a favor and don't work too much/hard. In the past I/we have lost 2 very good friends from this forum and the last thing I remember was, they were working hard on some addons/projects and it could have been just mere coincidence or just fact that they overworked themselfs till their body gave up. You maintain multiple addons, you work with me on the Point and Rewards module, Sloppy words cleaner and, and, and.... Long story short, watch your health and take enough rest so that we will be able to enjoy you and your work for many years to come. That goes for all of you out there. osC is nice and all but it won't bring you anything if you work yourself to death. Now back to work....
  25. 4 points
    It seems like every other question posted nowadays is about how to upgrade an older version of oscommerce and the op usually references the official version. This post is meant to provide a quick reference for how to convert an older shop to the current, recommended, one. First, the version that should be used is commonly called the Bootstrap, BS or Responsive version. It can be located here. One should not use the official version. The official version can be installed via the hosts control panel so it is easy to think that is the one to use - it is not. Since the BS version is not directly compatible with other versions, the following steps will be needed: Install the BS version into a new location Convert the database. See this thread for help with that. Install whatever addons the site needs. You need to be sure the addon will work with the BS version. This thread mentions specific ones but there are many others that will work. If in doubt, ask in the support thread for the addon in question. If you intend to use paypal, then install the Paypal App. At this point you should have a working shop. Test it thoroughly, especially the payment and shipping modules, before going live with it. When you are ready to go live, Mark your current shop as down for maintenance ( a simple index.html file is fine for this purpose ). Make a backup of the current shops database and files. Convert the database to the BS version. Replace all of the files with the new shops files. Edit the configure files so they work as the live shop. Remove the blocking page. If everything has gone correctly, the conversion should be complete.
×