Jump to content

altoid

♥Ambassador
  • Content count

    1,551
  • Joined

  • Last visited

  • Days Won

    13

Reputation Activity

  1. Like
    altoid reacted to raiwa in 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&featured-products-bs&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&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
  2. Like
    altoid reacted to burt in 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.
  3. Like
    altoid reacted to raiwa in Notes don't work   
    Discount Code BS 5.1.0 works with Phoenix:
     
     
  4. Like
    altoid reacted to raiwa in QTPro BS   
    Hello @artfulweb, 
    It needs to be updated for Phoenix. Please be patient. It's on my to do list
  5. Like
    altoid reacted to raiwa in Español pack para OsC Responsive BS EDGE o Gold   
    Uploaded Versión 1.0.1.4 for OSCOM CE Phoenix 1.0.1.4
    Español para OsC CE
  6. Like
    altoid reacted to burt in Bootstrap 3 is EOL   
    As of 24 July, BSv3 is EOL with no more security updates etc
    https://blog.getbootstrap.com/2019/07/24/lts-plan/
    This news should nudge you to at least look 👀 at Phoenix (BSv4 Shop Side) if you have not already done so.
  7. Like
    altoid reacted to burt in Phoenix, constructive feedback + bug hunting   
    Split out some discussions as they deserve a thread of their own (and weren't feedback or bug hunting 😎) 
     
  8. Like
    altoid reacted to burt in Sliding Product Listing Module   
    You can do anything you like...that's the beauty of the open codebase.  Go to it!
    Do note that I have plans to overhaul and simplify the code in the product_listing module at some point in the near future.
  9. Like
    altoid reacted to Mort-lemur in Products with no Orders   
    .....Well that was easier than I thought
    I now have a new field that shows how many have been ordered since day 1 against each product:
     

  10. Like
    altoid reacted to raiwa in Slim Checkout for BS   
    Tested and works with CE Phoenix 1.0.1.1. under PHP 7.3
  11. Like
    altoid reacted to raiwa in Modules Control   
    Module Control 1.2.0 tested with OSCOM CE Phoenix 1.0.1.1 under PHP 7.3 and works flawless.
  12. Like
    altoid reacted to raiwa in Products with no Orders   
    What about filter options:
    - products ordered: <,>,=,≠
    - products stock: <,>,=,≠
    - product status: 1, 0
    - products price: <,>,=,≠
    - date added: <,>,=,≠
    - date modified: <,>,=,≠
    makes sense?
  13. Like
    altoid reacted to burt in Phoenix Announcements   
    Phoenix 1.0.1.1 
    How to update
    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 Apply the 1.0.1.1 files -> 1.0.1.1.zip You could also simply download & install the latest v1.0.1.1
    https://github.com/gburton/Responsive-osCommerce/tree/1.0.1.1 and install it.
    You could make commit by commit changes
    1.0.1.0 to 1.0.1.1: https://github.com/gburton/Responsive-osCommerce/compare/1.0.1.0...1.0.1.1
    I suggest the simplest way (assuming you are on 1.0.1.0) is to grab the 1.0.1.1 zip, unzip it, and upload the files.
    Special Thanks
    to @Harald Ponce de Leon for the gzip fix to forum members for their constructive feedback and bug hunting Completely Uninstall Modules (if they are turned on)
    Admin > Modules > Header Tags > "Google+ Direct Connect Module" Admin > Modules > Social Bookmarks > "Google+ Share" Admin > Modules > Social Bookmarks > "Google+ +1 Button" Delete Files (after having turned off the modules above)
    includes/functions/gzip_compression.php  includes/modules/header_tags/ht_gpublisher.php includes/languages/english/modules/header_tags/ht_gpublisher.php includes/modules/social_bookmarks/sb_google_plus_one.php  includes/modules/social_bookmarks/sb_google_plus_share.php includes/languages/english/modules/social_bookmarks/sb_google_plus_one.php includes/languages/english/modules/social_bookmarks/sb_google_plus_share.php Enjoy.
  14. Like
    altoid reacted to Jack_mcs in Phoenix, constructive feedback + bug hunting   
    If it hasn't been mentioned, I suggest removing the Google+ Direct Connect module since they stopped Google+.
  15. Like
    altoid reacted to burt in Phoenix, constructive feedback + bug hunting   
    Sorry no, these particular images were not meant to be resized (I don't recall the exact reason why), which is why we pass null through the tep_image calls in that box.
     
    EDIT:
    Racking my brains trying to remember why these images were specifically taken out of a responsive/fluid approach, but I just can't remember.  To make them go fluid the correct approach would be
    remove this:
    , null, null, null, null, false
    from the tep_image call in the Box module.
    EDIT 2:
    If you could revert your change(s) and apply that change (and then test) that would be great, thanks.  If all looks well, I'll push it into 1.0.1.1
     
  16. Like
    altoid reacted to raiwa in Updating my site to Phoenix   
    The errors you report here are errors of your uncomplete update, they are not errors produced by the Phoenix 1.0.1.0 files. Please revise your update and try to replace complete files if possible.
    In general terms it would be easier to start from scratch with a clean Phoenix 1.0.1.0 installation. Then redo your modifications and add the addons you need. Consider that Phoenix is much more modular than your old store. So the installation of addons and other modifications are doen different than in your old store. Avoid core file changes like they were necessary in your old store, as much as possible.
    This error only existed in Phoenix 1.0.0.0. Please replace the complete file with the version supplied in 1.0.1.0 or higher. The wrong code is not visible in a normal text editor. You have to replace the whole file.
     
    Instead to add manually missing constants to the database, you'd better uninstall and reinstall the module. This is more safe.
  17. Like
    altoid reacted to burt in Discount Code BS   
    I truly believe that these sitewide hooks are a step forward  
  18. Like
    altoid reacted to raiwa in 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.
  19. Like
    altoid reacted to raiwa in Holiday-Promotional Message Add-On BS   
    Updated to Holiday-Promotional Message 3.0.0 BS
    Changes version 3.0.0:
    - Updated for CE Phoenix.
  20. Like
    altoid reacted to Harald Ponce de Leon in Legacy Code and PHP 7.3 Compatibility Checks (HOWTO)   
    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!
  21. Like
    altoid reacted to burt in 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 👍
  22. Like
    altoid reacted to burt in Naming Convention   
    I have PMd you.
  23. Like
    altoid reacted to burt in Phoenix, constructive feedback + bug hunting   
    Same error found in products_review_write as well.  Thank You.
    Will be pushed in 1.0.0.3
  24. Like
    altoid reacted to burt in Frozen   
    Frozen is now in Sunset Status with EOL slated for 31/12/2019.
    Phoenix is the default download from 4th July onwards.
     
  25. Like
    altoid reacted to fiodh in Fake accounts   
    Hi Jack I just want to say I don't hold you responsible for these problems  - your add on contribution has really helped tremendously. Thanks for all your work.
×