Jump to content

ozEworks

Partner
  • Content count

    1,465
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by ozEworks


  1. @bermuda 

    This line

     $this->host = ((MODULE_SHIPPING_UPSXML_RATES_MODE == 'Test') ? 'wwwcie.ups.com' : 'www.ups.com');

    should be changed to

    $this->host = ((MODULE_SHIPPING_UPSXML_RATES_MODE == 'Test') ? 'wwwcie.ups.com' : 'onlinetools.ups.com');

    and that should fix it.

    Just make sure you are editing upsxml.php and not some other older version. 

     

     


  2. I make the same comment as payment methods. Availability of shipping modules is a make or break deciding factor when choosing an ecommerce solution. Probably more so than payment.

    I believe it would be best to offer standalone and realtime. 

    Stand alone:

    Flat based on order value or weight

    Free based on order value

    Table rates, as per 2.3

    zones rates as per 2.3

    Real Time

    To be truly global the ideal is to offer a real time shipping module for the country’s government carrier.  So for US, is it USPS, for Canada it is Canada Post etc. At least for the top 10 osCommerce country users. You’d need to research that. 

    Any other method that is supported by the osCommerce team should be in the box and anything in the box should be free.

    For USA, people need FedEx and UPS and DHL.  

     

    For shipping it has to handle non-dimensional and dimensional shipping. It has to be able to configure the max weight per carrier. Freight has to be considered but anything that handles freight could be app store. 

    These are just my random thoughts on a Saturday morning 🙂
     

     

     


  3. Availability of payment methods is a deciding factor when choosing an ecommerce solution. If we want people to use os Commerce V4 versus other open source, we need to offer as many as possible free of charge out of the box - on and offline.

    In principal, I think all payment modules supported by the osCommerce team themselves should be included. Any not supported by them should be in the app store.

    All included should be free to use. 

    Offline needs to include Check.

    Online definitely needs to include Stripe. 

     


  4. It is good there is a focus on speed. Many solutions add features and then rely on hardware to make up for slow load times. We all know the story of Magento on that subject from years ago.  Shared hosting is still a reality for many open source users. 

    IMO, the pre-integrations would be better done as optional addons as storeowners have their own preferred tools for reviews eg yotpo (popular in US), ESPs (numerous) and chat (also  numerous). Preference is often based on their penetration into different markets. Not to mention the bad press Trust Pilot just got for millions of fake reviews they removed pre-float. 


  5. We has an issue with the Admin Approve process.  

    Warning: Error while sending QUERY packet. PID=21752 in /home/ozeworks/public_html/support/xxxxxx/admin/includes/functions/database.php on line 53
    2006 - MySQL server has gone away

    update fraudlabs_pro set fraudlabspro_status='APPROVE' where order_id = '5144'

    [TEP STOP]

    2006 - MySQL server has gone away

    select 1 from sessions where sesskey = '0bc4c6a91bbfca74f41060b7986defdc'

    [TEP STOP]

     

    Updating max_allowed_packet to 1GB did not fix.

    Looking at the https://apps.oscommerce.com/HboCa  V 1.3.5 must be out of date.

    Attached is our patched version. Tested on Fraudlabs Pro osCommerce 2.3. 

     

    FraudLabsPro_ozeworks_update.zip


  6. The bottom lins is Authroize.net wants people to move to their new API and I believe the core of that relates to recurring billing and customer records etc. to be PCI compliant both ends (site and authorize.net). 

    They are not going to let you use methods that violate PCI on their end. If you do recurring billing and/or use CIM, you will probably end up with a problem. 

    So at some stage the team need to develop a new Authorize.net module based on the new API.

     

     


  7. Authorize.net have announced AIM and SIM have reached end of life. They will no longer be supported but you will be able to keep using them..

    Specifically their APIs will remain available but not be upgraded. If any PCI compliance changes occur in the future (simple for example you had to collect Card Type as part of the transaction) these APIs will not meet them and you therefore would be not compliant if you continued to used them.

    Read full notice here https://support.authorize.net/s/article/Recurring-Billing-Flag-Rebill-Feature-End-of-Life-Overview

    There is new API available. See https://developer.authorize.net/api/  and osCOmmerce will need to work to provide a module to use with MS 2.2/2.3. 

    So bottom line there is no date associated with this.  Your payment modules will continue to work.  If/when an osCommerce Add On is released using the new API you should upgrade to it. 


  8. Just a note for people use the older MS2.2 / Rc2a USPS V4 module there are service name changes to Domestic you will need to make changing Standard Post to Retail Ground.  It will be in several places in the code.


     


    Also the name changes from being Registered Mark to a Trademark.


     


    'USPS Retail Ground tradmrk' => 'USPS Retail Ground tradmrk',


     


    Uninstall and reinstall to test.   Don't forget to keep your USPS ID to add back when you reinstall.


     


    See https://www.usps.com...lease-notes.rtf


     


    Other changes (Flat Rate boxes as a container) do not seem to impact the old module.


     


    Switch your current module to $usps_server = 'stg-production.shippingapis.com' to test impact



  9. Just a note for people use the older MS2.2 / Rc2a USPS V4 module there are service name changes to Domestic you will need to make changing Standard Post to Retail Ground.  It will be in several places in the code.

     

    Uninstall and reinstall to test.   Don't forget to keep your USPS ID to add back when you reinstall.

     

    See https://www.usps.com/business/web-tools-apis/2016-jan-webtools-release-notes.rtf

     

    Other changes (Flat Rate boxes as a container) do not seem to impact the old module.

     

    Switch your current module to $usps_server = 'stg-production.shippingapis.com' to test impact

×