Jump to content

Harald Ponce de Leon

  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by Harald Ponce de Leon

  1. Harald, does the auto update change anything with regards to the Street2 part of the address being captured? It's just that I vaguely remember Jack altering our installation to make sure we got the second line in the address (often when Aussies put their town/suburb name).


    It will overwrite files that have been modified. Here is a list of changes that will be performed:




    Click on the Files Changed tab and then the "40 changed files" link to view the file listing.


    I'll look at adding the suburb into SHIPTOSTREET2 in the upcoming update - this won't break existing installations. Could you get Jack to email me so we can go over the changes?

  2. For those upgrading, if v4.039 worked, then v5.000 will also work fine.


    For new installations that are getting deprecated notices, use the following error reporting level in includes/application_top.php and admin/includes/application_top.php:



    // set the level of error reporting
      error_reporting(E_ALL & ~E_NOTICE);
      if (defined('E_DEPRECATED')) {
        error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED);


    The error reporting is set at the top of those files. The code block above will be present in v2.3.5 onwards.

  3. It looks like you're using the latest development source code from out Github repository which is for v2.4.0beta.


    This release series will not work with existing modules for v2.3.x - a compatibility module is planned though and will be release in a short while.


    If you'd like to stick to the v2.4.0beta development code, try the latest source code from the PayPal App for v2.4 at https://github.com/haraldpdl/oscom2_app_paypal

  4. what should I set the Auto Return, Return URL to be ?  at the moment this is not set to a valid url.


    Anything really, as the right url is passed as a parameter to PayPal which overrides what is set in the PayPal profile.


    If the seller account is only used on the osCommerce store, then setting it to something like the following would not hurt:



  5. Hi Derek..


    Can you confirm that the PDT Identity Token has been setup on the PayPal Seller Profile and that the value is entered in the PayPal App -> Configure -> Payments Standard -> PDT Identity Token field?


    It needs to match the same value as on the live or sandbox account.


    PDT can be found on the following page at PayPal:


    Activating PDT


    To use PDT, you must activate PDT and Auto Return in your PayPal account profile. You must also acquire a PDT identity token, which is used in all PDT communication you send to PayPal.


    Follow these steps to configure your account for PDT:

    1.Log in to your PayPal account.

    2.Click the Profile subtab.

    3.Click Website Payment Preferences in the Seller Preferences column.

    4.Under Auto Return for Website Payments, click the On radio button.

    5.For the Return URL, enter the URL on your site that will receive the transaction ID posted by PayPal after a customer payment.

    6.Under Payment Data Transfer, click the On radio button.

    7.Click Save.

    8.Click Website Payment Preferences in the Seller Preferences column.

    9.Scroll down to the Payment Data Transfer section of the page to view your PDT identity token.

  6. I haven't experienced that with the App. Care was taken to properly migrate the old PayPal module parameters to the new App parameters and it also cleans itself up when modules are installed/uninstalled.


    After removing all parameters from the database, have you tried clicking around the App to see where the problem occurs?

  7. @@Mort-lemur thanks for the feedback!


    1) The App updates will not update admin/orders.php - it will only update it's own files in catalog/includes/apps/paypal/ and its module files in catalog/includes/modules/payment and catalog/ext/modules/payment/paypal/.


    This will also be a requirement in v2.4 when online updates are available to all Apps - they will only be able to update their own files.


    2) It's safe even on a shared hosting environment. If there's a hole in your home directory, then any type of damage is possible regardless if API Credentials are stored or not. In a worse case scenario its possible to generate a new set of API Credentials.


    3) Refunds are currently only possible on transactions that have been performed. So if a transaction came in for $30 - you could refund that transaction of $30. If you captured a partial amount of that $30, say $15, then you could refund that transaction of $15. A custom refund amount will be possible in one of the next App updates.

  8. Yes indeed I have the currencies defined with html entities:



    The retrieved information is correct:


    {"rpcStatus":1,"balance":{"EUR":"1.11 €","GBP":"£ 0.00","USD":"$ 0.00"}}


    {"rpcStatus":1,"balance":{"USD":"$ 1.05"}}

    If you viewed the HTML source on that raw output you would see the html entities there too. The App displays the amount with htmlspecialchars() as a precaution.


    What happens with your order emails, they too should contain $ as the same function is being used..?

  9. That's not a problem related to PayPal or any modules or osCommerce Online Merchant - it is simply a configuration problem with your installation.


    The cookie domain settings should not include http:// or https:// and should only be the domain names, so for the example you posted it should be:


    // limited to www.yourdomain.com
    define('HTTP_COOKIE_DOMAIN', 'www.yourdomain.com');
    define('HTTPS_COOKIE_DOMAIN', 'www.yourdomain.com');


    // available to all subdomains (minimum 2 dots required)
    define('HTTP_COOKIE_DOMAIN', '.yourdomain.com');
    define('HTTPS_COOKIE_DOMAIN', '.yourdomain.com');
    Leaving those values empty is also fine, however the results may differ between browsers.


    Hope that helps!

  10. Hi Mitchell..


    The PayPal App requires a later jQuery version than what is used by your Administration Tool template. You should try to update your jQuery version to at least v1.5.


    This can be done with the following steps:


    1) Download jQuery v1.11.1 from:


    2) Copy that file to:


    3) Update the jQuery version in the Administration Tool template. In the following file:




    <script type="text/javascript" src="<?php echo tep_catalog_href_link('ext/jquery/jquery-1.4.2.min.js'); ?>"></script>


    <script type="text/javascript" src="<?php echo tep_catalog_href_link('ext/jquery/jquery-1.11.1.min.js'); ?>"></script>
    Keep the v1.4.2 jQuery version in that directory as your shop template is more than likely using that jQuery version, which it can still keep using.

  11. @@LDeeJay - the Request API Credentials buttons are only shown if the store country is US or UK. This is defined in the Admin -> Configuration -> My Store -> Country configuration parameter.


    I don't know why "error_log_extraction" is reported when applying an update and am looking into it.


    To fix the OSCOM_APP_PAYPAL_EC_STATUS error, reset the App's configuration parameters by executing the following MySQL command:


    delete from configuration where configuration_key like 'OSCOM_APP_PAYPAL_%';
    You should be able to execute that via your hosting control panel or using phpMyAdmin.

  12. We're proud to announce the introduction of a new App endeavor with the release of PayPal App for osCommerce Online Merchant!


    We've worked in close collaboration with PayPal to not only bring you updated PayPal payment modules but have also bundled all PayPal modules, including Log In with PayPal, into a single App package for an even tighter integration with osCommerce Online Merchant to enhance both sellers and buyers experiences with PayPal.


    The PayPal App is optimized for and will be bundled with the upcoming osCommerce Online Merchant v2.3.5 release and can be installed on existing installations from v2.2RC2a to v2.3.4.


    The PayPal App has been architectured to preview and showcase the direction we are taking the new osCommerce Online Merchant v2.4 series in and how the new series will allow you to install and update Apps on your online store through the Administration Dashboard. The PayPal App includes an online update feature that can update itself with a click of a button that will be part of the core in v2.4 for all Apps to take advantage of.


    We are also extremely proud to be one of the first self-hosted e-commerce solutions to allow the PayPal App to configure itself by securely retrieving the PayPal account API Credentials for you. This is currently available for US and UK sellers and allows you to sign into or create a PayPal live or sandbox account to retrieve the API Credentials from. This makes it extremely easy for new PayPal sellers to start experiencing the PayPal payment methods through a sandbox account and to create a live account as soon as they are ready to accept payments - directly from the osCommerce Administration Dashboard.


    In addition, the PayPal App includes:


    - Updated payment modules

    - Payments Standard: Support for Payment Data Transfer (PDT) payments

    - Payments Standard: Stock management in IPN notifications

    - Order Administration: Capture full or partial authorizations, refund full or partial transactions

    - API Logging: All parameters sent in and received from API calls are logged


    Documentation for the PayPal App is available at:




    The PayPal App can be downloaded for free at:




    We look forward to your feedback on this announcement!


    Please post your feedback to this topic and any support related enquiries to the following channel: