Jump to content

ArtcoInc

Members
  • Content count

    1,838
  • Joined

  • Last visited

  • Days Won

    31

Reputation Activity

  1. Like
    ArtcoInc got a reaction from burt in Phoenix NavBar CSS   
    *** Update ***
    Ok, as I found yesterday, in Admin->Modules->Content->Navigation Bar, you can select from several pre-set color combinations. However, if you want to use a different color combination, add this to your user.css file:
    .cm-navbar { background-color: blue !important; } .nav-link, .navbar-brand , #navDropdownAccount, #navDropdownCurrencies, #navDropdownCart, #navDropdownLanguages { color: red !important; } .nav-link:hover, .navbar-brand:hover, #navDropdownAccount:hover, #navDropdownCurrencies:hover, #navDropdownCart:hover, #navDropdownLanguages:hover { color: white !important; } This covers all of the stock NavBar modules included with Phoenix. Obviously, you can (should!) change the colors to your liking.
    I hope this helps anyone setting up Phoenix, and want to color things up a bit 😀
    Malcolm
     
    ** update to the update **
    This covers all of the stock NavBar modules EXCEPT for the 'hamburger' button. For that, see my post below.
  2. Like
    ArtcoInc 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.
  3. Like
    ArtcoInc reacted to raiwa in Optional Related Products, Version 4.0   
    Uloaded update for Phoenix 1.0.1.x:
    Related Products Phoenix 7.0
    Update Version Phoenix 7.0:
    - Updated for CE Phoenix 1.0.1.x
    - fixed undefined warning in admin/optional_related_products.php if product info module is not installed.
    - updated template class in product info module to core naming convention "cm-pi-related_product"
    - update structured database
    - added config entries for columns/viewport like also purchased products module.
    - removed obsolete height control config entries.
    - moved html to template
    - general file cleaning (tabs/spaces, UNIX new line)
  4. Like
    ArtcoInc reacted to raiwa in Wholesale (SPPC lite)   
    Uploaded update for Phoenix:
    Wholesale (SPPC lite)
    Version 4.0.0.:
    -  Update for Phoenix 1.0.1.x
    Compatibility: Phoenix 1.0.1.x PHP 7.0-7.3
    -------------------------------------------------------------------------------------------------------------
    CE FROZEN please use Wholesale (SPPC Lite)  3.0.4
    Older 2.3.4.(1.) versions please use Wholesale (SPPC Lite) 2.0
  5. Like
    ArtcoInc reacted to burt in edge to phoenix update   
    A very long extension lead and a laptop.  And a few cocktails.
  6. Like
    ArtcoInc reacted to raiwa in [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
     
  7. Like
    ArtcoInc reacted to Jack_mcs in Category Images   
    That addon only works in BS3 shops because it uses the "equal-height" class and that class is not used in BS4 (Phoenix). I haven't looked at the code in Phoenix to see how that problem is handled but the following should allow that addon to work. In the includes/modules/content/index/templates/category_images.php file, change this line
    <div class="card-body category-images-item"> to
    <div class="card-body equal-height category-images-item"> But to be clear, the main reason the two boxes are so different in height is because the second one is missing the image. If you add an image for it that might fix the problem. If you don't have an image for a particular category, creating one for a replacement, like "No Image Available" would be the best choice.
  8. Like
    ArtcoInc reacted to Jack_mcs in Category Images   
    Yes, that is correct. The "equal-height" added to the code is just a flag to tell the equal height module where to look. They are both required for it to work. You will also need to make the code change in the other template files for this addon as well if the problem is seen for them. That part of the code is the same in each so it should be easy to find.
    Thanks for posting that it worked.
  9. Like
    ArtcoInc got a reaction from valquiria23 in Store Search Bar (BS)   
    @tgely
    Is there any chance that you will be updating this to BootStrap v4, to be used in the latest Phoenix release of osC?
    In this add-on, you have a file called bootstrap3-typeahead.min.js. I have concerns of how this will work under the new Bootstrap v4.
    TIA
    Malcolm
  10. Like
    ArtcoInc reacted to burt in New installation - which one to choose?   
    That's right.
    It is the official Community Edition of osCommerce, accepted and authorised by the owner of osCommerce and available from the official osCommerce downloads page. 
    You can't get much better than that for a Community supported edition.
  11. Like
    ArtcoInc 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.
  12. Like
    ArtcoInc 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 👍
  13. Like
    ArtcoInc 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!
  14. Like
    ArtcoInc reacted to Jack_mcs in 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.  
  15. Like
    ArtcoInc reacted to burt in Naming Convention   
    There seems to be some confusion over the Naming Convention chosen...so, as posted elsewhere, let's set the record straight;
    I originally called it "BS" as a bit of a joke.  I still like that name as it stands for *cough*BS*cough* err BootStrap.
    When it got quasi-official acceptance, that was changed to "CE" which stands for Community Edition.  
    Under the umbrella of CE is (as of today) ONE release;
    PHOENIX [ https://github.com/gburton/Responsive-osCommerce/archive/master.zip ]
    Bootstrap v4.  There are also two development Tags which were fixed points in the timeline to release of Phoenix;
    GOLD [ https://github.com/gburton/Responsive-osCommerce/archive/v2.3.4-GOLD.zip ]
    Bootstrap v3.  FROZEN [ https://github.com/gburton/Responsive-osCommerce/archive/2341-Frozen.zip ]
    Bootstrap v3, with more modularity.  Simple, isn't it  Well, I think so even if you don't.
  16. Like
    ArtcoInc reacted to Harald Ponce de Leon in Naming Convention   
    Every v2.x release is being sunsetted, including v2.4. Someone is welcome to continue development through the Community Edition program. My focus is 100% on v3.
    All Community Edition releases will have their own support area in the forum and their own version in the Marketplace. Linking to the releases on our downloads page is just the start - it is planned to have dedicated pages for each release so their features can be showcased.
  17. Like
    ArtcoInc reacted to Harald Ponce de Leon in 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.
     
  18. Like
    ArtcoInc reacted to Jack_mcs in Message Box   
    I think interest in it is high so I suspect addons will be converted more quickly than with the VS3 version. At least, I hope so. :)
  19. Like
    ArtcoInc got a reaction from valquiria23 in Message Box   
    @Jack_mcs
    Thank you for your support of the Phoenix project!
    M
  20. Like
    ArtcoInc reacted to burt in Phoenix Announcements   
    CE Phoenix
    Phoenix is the Master Community Version of osCommerce

    https://github.com/gburton/Responsive-osCommerce/releases
    https://www.oscommerce.com/Products
    Demo Site
    https://template.me.uk/phoenix/index.php
    External Libraries
    https://github.com/gburton/Responsive-osCommerce/wiki/External-Libraries
    PHP Version
    Minimum Maximum 7.0 7.1.x Image Credits
    Images in the default installation are copyright their respective owners;
    Image Owner osCommerce Logo osCommerce Phoenix Logo G Burton Oranges Eelffica from Pixabay Lemons Eelffica from Pixabay Pears Eelffica from Pixabay Apples Eelffica from Pixabay Tomatoes Rocky_H from Pixabay Heart Gerhard Gellinger from Pixabay Thank You
    To all shopowners, developers, consultants and business owners who have supported the project over the years.
    Beer Tokens
    "Beer Tokens" are not used to purchase beer - they are used to give time into the Project. I am hopeful that enough shopowners, developers, consultants and businesses ... will join the Phoenix Club to allow two professional developers to work on the code on an ad-hoc basis.
    Join the Phoenix Club
    If you wish to sponsor ongoing and future development, please consider joining the club https://forums.oscommerce.com/clubs/1-phoenix/
  21. Like
    ArtcoInc 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.
     
  22. Like
    ArtcoInc got a reaction from burt in How to remove 'sort by - grid - list'   
    @burt @Heatherbell
    What I had done essentially was option A (I commented it out instead of actually deleting it). But, IMHO, option B would be a better way to do it.
    @burt !
    M
  23. Like
    ArtcoInc reacted to burt in How to remove 'sort by - grid - list'   
    OK, I did miss that...
    You've a couple of options, note that I have not tried any of them so syntax may be a little out - but it should give you ideas;
    A.  remove the code by amending core code (note that is nothing "bad" about core code changes, I just advise to do it as little as possible and then to try to remember what you did for future reference). 
    - remove this block of code: 
    https://github.com/gburton/Responsive-osCommerce/blob/master/includes/modules/product_listing.php#L40-L103
    B. hide that same block of code using .css
    - add this to user.css:  
    div.alert-filters { display: none !important; }
    C. hide that same block of code using javascript
    - add this to that ggi.php that I had you create earlier in the thread: 
    $('div.alert-filters').hide();
    As mentioned, syntax may be out but gives the general idea.  Of the three, I'd likely do it in the .css if it was me.
     
     
  24. Like
    ArtcoInc got a reaction from oscmepwl in Remove items from cart   
    @JACUK
    fwiw ...
    I modified my Shopping Cart drop-down to include a 'Checkout' link, and removed the 'Checkout' from the NavBar ...

    I think that it's better for the customer to View their cart, and then can remove items individually there. But, it's your store ...
    .....
    Thinking about it more, as shown above, the part number in the drop-down is a link to that item's page. Depending on the length of your part numbers, and the size of your drop-down, I don't see why you couldn't add a small 'Delete from Cart' button between each part number and the cost. Coding that would be up to you, of course.
    HTH
    M
  25. Thanks
    ArtcoInc got a reaction from puggybelle in Need help fixing an old contrib - Report Missing and Unassigned Images   
    @puggybelle
    In the latest Community Edition, many of the paths are now hard coded. Find:
    $image_directory = DIR_FS_CATALOG . DIR_WS_IMAGES; and try changing it to something like this:
    $image_directory = DIR_FS_CATALOG . 'images/' ; (you may have to play with the leading and trailing '/' )
    HTH
    Malcolm
×