Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 01/25/2019 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
    raiwa

    List of my Phoenix compatible Addons

    Phoenix ready Addons: The following free Addons are updated for Phoenix and available on the Marketplace: Spanish Language Pack: https://apps.oscommerce.com/f8hiQ&espanol-para-osc-ce https://github.com/raiwa/OSCOM-CE-Phoenix-Spanish-language-idioma-espanol Recently Viewed Products: https://apps.oscommerce.com/z7iA8&recently-viewed-products-ce Related Products: https://apps.oscommerce.com/y0rDZ&related-products-ce Featured Products: https://apps.oscommerce.com/TyAIr&amp;featured-products-bs&amp;p=2 Holiday Message: https://apps.oscommerce.com/G3NiL&holiday-promotional-message-ce Shop by Price: https://apps.oscommerce.com/Lia0H&shop-by-price-ce Wholesale Lite https://apps.oscommerce.com/VWUpG&wholesale-sppc-lite Discount Codes https://apps.oscommerce.com/iIUE4&amp;discount-codes-bs Checked and compatible with Phoenix: Slim Checkout: https://apps.oscommerce.com/pgaC2&slim-checkout Modules Control: https://apps.oscommerce.com/FM65c&modules-control Coming soon: KissIt Image Thumbnailer only one small update needed see: https://forums.oscommerce.com/topic/388022-kissit-image-thumnailer/?do=findComment&comment=1790276 PWA (Purchase without account – Guest Checkout) QTPro Reviews Navbar Header Module Store Hotline Store Mode Sloppy Words Cleaner I’ll keep this lists updated when I’ll have ready new modules for Phoenix
  3. 8 points
    burt

    Phoenix Announcements

    Phoenix 1.0.1.0 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 Make sure you have applied the 1.0.0.4 hotfixes -> 1.0.0.4.zip Apply the 1.0.1.0 files -> 1.0.1.0.zip You could also simply download & install the latest v1.0.1.0 https://github.com/gburton/Responsive-osCommerce/tree/1.0.1.0 and install it. You could make commit by commit changes 1.0.0.4 to 1.0.1.0: https://github.com/gburton/Responsive-osCommerce/compare/1.0.0.4...1.0.1.0 I suggest the simplest way (assuming you are on 1.0.0.4) is to grab the 1.0.1.0 zip, unzip it, and upload the files. Special Thanks to @raiwa for collating and updating the modular shopping_cart to @raiwa @Tsimi @kymation @Dan Cole for their original modular shopping_cart files Notes As this is a feature release, you must also go into admin and install the shopping_cart module(s) if you are upgrading. Admin > Modules > Content > {Install} - and you will find them. As usual, these modules are configurable by sort order, width etc. Enjoy.
  4. 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/
  5. 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.
  6. 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".
  7. 6 points
    peterpil19

    Ancient Coin Traders - Phoenix

    Dear All, My website has been upgraded to Phoenix (latest version). www.ancientcointraders.com It was previously Edge BS3 (pre-frozen). Main improvements are: 1. much faster 2. new features in Phoenix (sitewide hooks, modular shopping cart, product_info pages, improved modules etc.) make life easier. 3. Bootstrap 4 has much neater ways of doing things than Bootstrap 3. Shorthand classes in particular make things cleaner and simpler. Bootstrap 4 is also mobile first. A special thank you to @burt for accepting my request to assist me with what was a very quick 'migration' to Phoenix. This involved starting off fresh with Phoenix, making change and cleaning up all my blundered custom 'coding' from my BS3 installation. Thank you also to @burt for keeping the project alive. I have done a lot of comparisons recently against other open-source and commercialised shopping cart software. I also habitually look closely at any website I am on as I am sure many others here do. Phoenix holds its own against most others. You can get a nice-looking website up and running fairly quickly from scratch. Happy as always for any feedback or areas of improvement. Regards, Peter Note: I could not edit my original post on this board for some reason, so happy of course for them to me merged if a moderator obliges.
  8. 6 points
    burt

    Phoenix Announcements

    Phoenix 1.0.2.1 Join the Phoenix Club https://forums.oscommerce.com/clubs/1-phoenix/ This Update Fixes bug in one of the product listing files - TY @raiwa for heads up Deprecate custom.css - A few HTML changes in some files to accommodate this Fixes bug in data-price in a couple of places - TY @raiwa for heads up Adds RU language fileset link in Readme - TY @Fredi Update FA - To 5.10.1 Fix Sort By Bug in products_new.php - TY @Heatherbell for heads up Modernise Reviews - Deprecate reviews.php - Deprecate product_reviews_info.php - Remove links to the above pages - Prettify and Pre-install Reviews module on product_info.php - Move "write review" into /ext/ - Make stars "gold" Update Version - To 1.0.2.1 Special Thanks to Forum members for constructive feedback and bug hunting to Phoenix Club members for constructive feedback on the new Layout to @cupidare @raiwa @Fredi for maintenance of language filesets Notes for Language Maintainers @cupidare DE @raiwa ES @Fredi RU /includes/languages/english.php /includes/languages/english/modules/boxes/bm_reviews.php /includes/languages/english/modules/content/footer_suffix/cm_footer_extra_copyright.php /includes/languages/english/modules/content/product_info/cm_pi_reviews.php /includes/languages/english/modules/content/reviews/write.php How to update ZIP FILE, easy upload. Find out what version you are on now; admin > tools > version checker, then perform the necessary updates; Make sure you have applied the 1.0.0.1 hotfixes Make sure you have applied the 1.0.0.2 hotfixes Make sure you have applied the 1.0.0.3 hotfixes Make sure you have applied the 1.0.0.4 hotfixes Make sure you have applied the 1.0.1.0 hotfixes Make sure you have applied the 1.0.1.1 hotfixes Make sure you have applied the 1.0.1.2 hotfixes Make sure you have applied the 1.0.1.3 hotfixes Make sure you have applied the 1.0.1.4 hotfixes Make sure you have applied the 1.0.2.0 hotfixes All previous hotfix zips are listed in this thread. EG, if you are on 1.0.1.0, you must perform 1.0.1.1 hotfix to the latest listed hotfix, then; Apply the 1.0.2.1 changes -> 1.0.2.1.zip Read and perform the "if updating an existing phoenix" section DOWNLOAD AND INSTALL FULL VERSION You could simply download & install the latest full v1.0.2.1 https://github.com/gburton/Responsive-osCommerce/tree/1.0.2.1 COMMIT BY COMMIT (MANUAL CHANGES) 1.0.2.0 to 1.0.2.1: https://github.com/gburton/CE-Phoenix/compare/1.0.2.0...1.0.2.1 WHAT IS SIMPLEST I suggest the simplest way (assuming you are on 1.0.2.0) is to grab the 1.0.2.1 zip, unzip it, and upload the files. If Updating an Existing Phoenix Make sure that you have first updated fileset to 1.0.2.1 (by either manual commit, or uploading zip), then, doing this in order; 1. Install New Modules There are no NEW modules to install 2. Uninstall Existing Modules Completely turn off (uninstall), if you have them installed Admin > Modules > Content > Reviews Button Admin > Modules > Navbar Modules > Review Link 3. Reinstall Existing Modules Completely TURN OFF (uninstall) and THEN TURN ON (reinstall) the following module(s); Admin > Modules > Boxes > Reviews aka bm_reviews Admin > Modules > Content > product_info > Reviews aka cm_pi_also_purchased 4. Delete Obsolete Files includes/languages/english/modules/content/product_info/cm_pi_review_button.php includes/languages/english/modules/navbar_modules/nb_reviews.php includes/languages/english/product_reviews.php includes/languages/english/product_reviews_write.php includes/languages/english/reviews.php includes/modules/content/product_info/cm_pi_review_button.php includes/modules/content/product_info/templates/tpl_cm_pi_review_button.php includes/modules/navbar_modules/nb_reviews.php includes/modules/navbar_modules/templates/tpl_nb_reviews.php product_reviews.php product_reviews_write.php reviews.php custom.css 5. Run SQL There is no SQL that needs to be changed. Enjoy!
  9. 6 points
    raiwa

    Do I have to reinstall <sigh>

    I'm doing all addon updates and development on a local PHP 7.3.2 installation with Phoenix 1.0.0.4 and since today 1.0.1.0 and no problems until now.
  10. 6 points
    raiwa

    Discount Code BS

    New version uploaded: Version 5.1.0 Phoenix Changes: Removed support for earlier EDGE versions Fix for discount not showing on first page load in ship in cart order total module in shopping cart, disable "Apply" button until code is validated. Added sitewide hook for session unregister of discount code on logoff ( @burt, sitewide hook used for the first time 😀) This Package will be separated in a neew addon, once a proper label for Phoenix version is available.
  11. 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.
  12. 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
  13. 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.
  14. 5 points
    General support/feedback for Bootstrap 4 admin See https://apps.oscommerce.com/LCrov&amp;bootstrap-v4-oscommerce-admin-ce
  15. 5 points
    puddlec

    TinyMCE

    this is what i managed to achieve. With my first attempt at using the hook system i'll possibly tidy it up a bit on Sunday. and upload it as an addon basically it just works just like the hooks on the shop side. works on all category description, and product descriptions textareas, regardless of how many languages you use. in regards to the themes / plugins / toolbar you can just add / remove them as you see fit (the settings you see in the file are the ones i use myself) it does with work the tinymce CDN (if you got an API KEY), loading locally, or via another CDN (using an CDNJS just to show it works), you can use whatever source you want. the same basic idea can also be used for ck editor, or any other javascript library you think you may need within the admin. tinymce hook.zip
  16. 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 👍
  17. 5 points
    The next update will be pushed out this month and takes care of that 👍
  18. 4 points
    JcM CKEditor V1.0 A simple add-on to let you place a WYSIWYG HTML editor onto your site’s admin. CKEditor 4 Proven, enterprise-grade WYSIWYG HTML editor with wide browser compatibility, including legacy browsers. Paste from Word and Excel, spell check, accessibility checker, tables. Autocomplete, @mentions, widgets, code snippets, emoji 😊 plugins. Full control over content: HTML filtering, view source mode. Great accessibility: WCAG 2.0 AA and Section 508 compliant. Long-term support (LTS) until 2023. For Phoenix simply copy new files into the required places and your done. You can if you like do it the old fashion way as in the frozen method below. For frozen it’s a simple edit of one template file, open :- public_html/admin/includes/template_bottom.php and just before the </body> add this code, <script src="https://cdn.ckeditor.com/4.12.1/standard/ckeditor.js"></script> <script> CKEDITOR.replace( "products_description[1]" ); CKEDITOR.replace( "manufacturers_description[1]" ); CKEDITOR.replace( "categories_description[1]" ); </script> That’s it your done. If you go to admin and edit a product you will see the WYSIWYG HTML editor on the product description box. This is just a simple application of the editor you can expand it as much as you like. It has been tested on Phoenix 1.0.2.0 only. It should however work on other versions and frozen Enjoy.
  19. 4 points
    greasemonkey

    Facebook Messenger Chat Box Addon

    I've developed a neat little header tag module that drops a Facebook messenger chat box into your site - so much easier than trying to get one of the live chat addons to work and its free. Connects to your Facebook (business) Page simply. I've tried it on EDGE and PHOENIX and it works perfectly (I'm sure it will work on any version... but haven't tested it). Configurable to have the chat box open on load or not (showing the Facebook Messenger Icon only). The only thing you need is your Facebook Page ID which can be found with following instructions: To find your Page ID: From News Feed, click Pages in the left side menu. Click your Page name to go to your Page. Click About in the left column. If you don't see About in the left column, click See More Scroll down to find your Page ID below More Info. Quick Edit - some need to whitelist their domains within their Facebook page: Click Settings at the top of your Page Click Messenger Platform on the left Edit whitelisted domains for your page in the Whitelisted Domains section Screencap attached Addon found here: https://apps.oscommerce.com/Apps&amp;e18Iy&amp;facebook-messenger-chat-box-addon
  20. 4 points
    burt

    Product Page Layout

    Product Page Layout is in finalised testing; https://template.me.uk/phoenix/product_info.php?products_id=3 This all-new system allows millions (that is not an exaggeration) of layout possibilities, all easily set up by shopowner.
  21. 4 points
    burt

    Upgrade Path TO Phoenix

    At this moment, today...Phoenix is the only viable option for a shopowner who wants a php7 ready and responsive version of osCommerce. I work on Phoenix every day, pushing it forward as best I can and I have a good group of shopowners and developers backing me up and giving ideas and advice. If I wanted to start up a shop or to update an older osC version, I would utilise Phoenix and become involved in where it goes next.
  22. 4 points
    JcM Color Tweak V1.1 Updated to clean code and fix errors. Remove old and install new Header tag. This is an add-on that makes the process of changing colors on your website a little simpler. Once installed you can make changes to the site colors from admin. You can change most common item. Some items such as navbar can have a color or an image. Text color can also be set for most items. This is work in progress and more items will be added over time. When making color changes it helps to pick a color palette to work from as this produces a better result. In the add-on I have used the face-book palette as the defaults. Again totally standalone with no core code change. Simply copy all files into relevant sections and go to admin and install. Has been tested on Phoenix V1.0.1.1 and Frozen only. Can be seen working on my custom test site NOTE: This is NOT the official test site
  23. 4 points
    raiwa

    [Contribution] Ship In Cart

    Phoenix update uploaded: Ship In Cart CE reloaded Changes Vers. 5.0: - Update for Phoenix 1.0.x.x - html code moved to template
  24. 4 points
    burt

    Email queuing system

    Real life feedback/ideas from shopowners lead me to this change; With one extra line of code in the main module I made this a reality, so now it's possible to use the {{TAG}} system in the Title as so: and when received looks like (eg) this: Pretty damned cool!
  25. 4 points
    burt

    Email queuing system

    And here's the Slug page, aka email templates... So, just one more thing to do...send out emails at about the right time, and make sure the emails use the merge_vars as shown (anyone who runs Mandrill will understand merge_vars). But in this relatively simple system, assuming an email was going out to Donald Duck, the word {{FNAME}} would be replaced with "Donald". So, next step is to tie it all together and see if the concept works...
×