Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Leaderboard

Popular Content

Showing content with the highest reputation on 11/17/2020 in all areas

  1. Jack_mcs

    Jssor Slider

    A new version has been uploaded with these changes: Added code to delay javascript to make it compatible with Phoenix. Changed code to be compatible with the new advert system (Phoenix only). Changed code to allow text to be shown on the banners. Moved the jssor images to the correct location to match the code.
    2 points
  2. Jack_mcs

    Sitemap SEO

    A new version had been uploaded with these changes: Added a icon for the left column for Phoenix. Changed code to only show active products. Found by member @koopmanh. Changed code to fix php warnings. Corrected error in function declaration in admin. Moved the stylesheet file to ext/css/. Please note that this update only contains changes for Phoenix. It has been tested with V 1.0.7.10.
    2 points
  3. Uploaded: Ajax Attribute Manager 3.3.2 Requires: OsCommerce Phoenix 1.0.7.10+ REQUIRED! PHP 7.0 to 7.4 Changes Version 3.3.2.: + added support for Phoenix 1.0.7.10 core sort order + removed optional product_options_sort_order support + added auto update script for product_options_sort_order to core sort order columns. + normalized spacing and indents. + updated custom database functions to use core functions. + modernized coding to match core standards ********************************************************************* If you were using attributes/options sort order from previous versions: - Make a database backup for security if something gets messed up. - On first load of this version, the old sort order entries will be migrated to the new core sort order columns. - Check your database for success after you loaded the new attributes manager. - Use the product info options/attributes sort order content module included in Phoenix 1.0.7.10 *********************************************************************
    1 point
  4. cdetdi

    Google reCAPTCHA v3

    Small nit: For v3 Recaptcha Google recommends enabling the tracking code on EVERY page load, not just ones you want to protect. This enables Google to create a traffic profile. e.g. if a customer has been shopping the site normally but then submits a contact us in a suspicious way (e.g. did a copy-paste autofill which was very fast) Google takes into account the non-spammy behavior beforehand. It looks like your module only loads on the hooked pages, I suggest loading the tracking code on all pages following Google's guidance.
    1 point
×
×
  • Create New...