Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

peterbuzzin

Members
  • Posts

    141
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by peterbuzzin

  1. Hi, Sounds like you're not using v2.4.3.1 default install in that case. Can you post the contents of the bottom half of checkout_confirmation.php I don't need all of it, but if providing all of it is easier then do that. And/or post a link to your site so I can can make sure jQuery/jQuery UI is being used and where it's loaded in the page (I only need to look at the html source view of the index page in the browser for this). Alternatively if you're comfortable detecting where jQuery and jQuery UI is loaded yourself, find out if it's being loaded in <head> tags. If it's loaded in <head> tags then feel free to pasted that code anywhere towards the bottom of checkout_confirmation.php preferably after the closing </form> tag for the checkout confirmation page.
  2. @pete2007 You need some javascript/jquery to disable the button once clicked. In checkout_confirmation.php add this to the bottom of the page. I've made this based on a default install of v2.4.3.1 and will work providing your store still uses jQuery and jQuery UI Find: <script type="text/javascript"> $('#coProgressBar').progressbar({ value: 100 }); </script> Add this beneath it (do not replace, just add beneath): <script> $('form[name=checkout_confirmation]').submit(function(){ var btnLoadingTxt = 'Loading Please Wait'; var confirmationForm = $(this); $(this).find('button[type=submit]').each(function (index) { var btnHtml = $(this).html(); $(this).clone(false).attr('id', 'disabledBtn').prop('disabled', true).html(btnHtml).insertBefore($(this)); $('#disabledBtn .ui-button-text').text(btnLoadingTxt); $(this).hide(); confirmationForm.prepend($(this)); }); }); </script> With the above script, once the form is submitted it will copy the styling and text displayed of the original button, clone it and make the cloned button disabled. It then hides the original submit button and changes the text of the cloned button to "Loading Please Wait".
  3. Hi @douglaswalker All cacerts work independent of PayPal (so yes it will work, just copy the contents out of cacert.pem and paste into paypal.com.crt), it contains encryption keys and allows secure communications between two different endpoints (remote servers/services for example). The server making a request will use one of the keys and the destination needs to have the corresponding matching key and if both are present then they can talk to each other securely. (If you open the file in Notepad or similar and look through it you'll see the keys and the Cert Authorities that provided them). Over time encryption keys are replaced or retired due to vulnerabilities or greater technology. If you continue using an old cacert you notice eventually that you'd be able to communicate with less and less endpoints (PayPal for example) as the destination endpoints will remove old keys and add new ones as time goes on. So unless you update the cacert every now and then you'll find you wont be able to communicate with the new keys because you don't have that key in your cacert. An example of this is if you download and install PayPall App it comes with a cacert but if you attempt to use the Test found in PayPal > Configure > General > SSL Version - Test Connection Button it will fail because the cacert that comes with the PayPal App is really old and most endpoints will refuse to support the keys in it. As soon as you upload a new one it will work again (providing you use TLS 1.2 setting as most don't support "Default" which I think is SSL2/3 which was retired some time ago and again something else that needs removing from the "official" App).
  4. You should also replace the standard includes/cacert.pem with the latest one also if you haven't already, it gets used for curl operations within the store and it's way out of date too. You can download the latest version it from here https://curl.haxx.se/docs/caextract.html
  5. Sorry to be a bit political and off-topic but that one person has a god complex, is a protectionist and it's annoyed me for almost 15+years. As a full time PHP developer myself I can appreciate it's his "baby" and he's probably made a lot of money indirectly from it (who wouldn't want it on their CV) and has lots of better opportunities to use his time on, but the "baby" is now neglected and if it were a real baby child protection would have stepped in a long time ago. His addons are protected so even when they no longer work because of service provider deprecation/changes or even have bugs (he's not perfect) nothing can be done to update them (Worldpay and PayPal App for example) but they're still advertised as the latest and official.
  6. Hi MrPhil, If you need assistance, could you create a separate topic for it and provide the files, I may have time to look at it. This is intended for the default PayPal App v5.018 as found here https://apps.oscommerce.com/fZMiN&paypal-app (although you can't actually download v5.018 from here you have to auto-update once installed which has always bugged me, every version should be available on there. And another annoyance is when you download osCommerce 2.3.4.1 it doesn't come with the PayPal App). This will help keep this topic on point and prevent others who might be less technical from getting the code mixed up/confused.
  7. It does indeed! The link generated by PayPal is dynamically produced from code and then inserted in the page on load. The link is something like <a id="LIwPP41972473" class="LIwPP_V2 PPBlue_V2 CWPP_rectangle CWPP_medium" text="Connect with PayPal" href="#"><lots of code in here></a>. Unfortunately because that link and html is generated at PayPal and sent back to the store there's not a lot that can be done to it. Notice the href="#" in the a tag? That's what's making it go to the homepage because the <base href="https://www.exoticincense.com/"> (in your case) is set to the domain root and relative URL's will always combine with the base href giving you https://www.exoticincense.com/#. You can't change this as it will break your CSS, JS and image paths etc. The second theory is that it's being done via PayPal javascript, but again because it's all generated by PayPal it's a lot of time/effort to look into and possibly change and my priority was to get it working again. However, things like this do trigger my OCD, so you never know I may update the post at some point with a workaround lol.
  8. Please see my last post above. The forum changed 3 items of code when posting and may produce unpredictable results if left as is.
  9. Hi, you are entirely correct, well spotted and that is odd! When using the code tags in this forum, if you edit the content of a code tag after setting it (which I did a few times), it translates the &amp; into &. Annoying!! Correct code below, unfortunately the forum isn't allowing me to edit my posts any longer. ANYONE READING THIS FOR THE FIRST TIME USE THE INSTRUCTIONS AND CODE BELOW AND NOT THE CODE ABOVE First of all in your store admin, make sure Telephone Number and Seamless Checkout is unticked, then save the settings. Note: Possible ongoing problems. Seamless checkout previously allowed users who have logged in via "Log In with PayPal" to continue to make payment without logging in again. As PayPal has removed Seamless as a scope item I'm not sure if customers will have to login again to PayPal once they get to payment method selection or click a Checkout with PayPal button. The new connect/api.js may compensate for this automatically but I haven't tested that far yet so cannot comment either way. In includes/modules/content/login/templates/paypal_login starting line 18 Find: <script type="text/javascript" src="https://www.paypalobjects.com/js/external/api.js"></script> <script type="text/javascript"> paypal.use( ["login"], function(login) { login.render ({ <?php if ( OSCOM_APP_PAYPAL_LOGIN_STATUS == '0' ) { echo ' "authend": "sandbox",'; } if ( OSCOM_APP_PAYPAL_LOGIN_THEME == 'Neutral' ) { echo ' "theme": "neutral",'; } ?> "locale": "<?php echo $cm_paypal_login->_app->getDef('module_login_language_locale'); ?>", "appid": "<?php echo (OSCOM_APP_PAYPAL_LOGIN_STATUS == '1') ? OSCOM_APP_PAYPAL_LOGIN_LIVE_CLIENT_ID : OSCOM_APP_PAYPAL_LOGIN_SANDBOX_CLIENT_ID; ?>", "scopes": "<?php echo implode(' ', $use_scopes); ?>", "containerid": "PayPalLoginButton", "returnurl": "<?php echo str_replace('&amp;', '&', tep_href_link(FILENAME_LOGIN, 'action=paypal_login', 'SSL', false)); ?>" }); }); </script> Replace with: <script type="text/javascript" src="https://www.paypalobjects.com/js/external/connect/api.js"></script> <script type="text/javascript"> paypal.use( ["login"], function(login) { login.render ({ <?php if ( OSCOM_APP_PAYPAL_LOGIN_STATUS == '0' ) { echo ' "authend": "sandbox",'; } if ( OSCOM_APP_PAYPAL_LOGIN_THEME == 'Neutral' ) { echo ' "theme": "neutral",'; } ?> "responseType" : "code id_Token", "locale": "<?php echo $cm_paypal_login->_app->getDef('module_login_language_locale'); ?>", "appid": "<?php echo (OSCOM_APP_PAYPAL_LOGIN_STATUS == '1') ? OSCOM_APP_PAYPAL_LOGIN_LIVE_CLIENT_ID : OSCOM_APP_PAYPAL_LOGIN_SANDBOX_CLIENT_ID; ?>", "scopes": "<?php echo implode(' ', $use_scopes); ?>", "buttonType" : "CWP", "buttonShape" : "rectangle", "buttonSize" : "md", "fullPage" : "false", "containerid": "PayPalLoginButton", "returnurl": "<?php echo str_replace('&amp;', '&', tep_href_link(FILENAME_LOGIN, 'action=paypal_login', 'SSL', false)); ?>" }); }); </script> In includes/modules/content/login/cm_paypal_login.php on line 259 (to prevent a blank/white screen once a user has logged in via PayPal when returning to the store). Find: echo '<script>window.opener.location.href="' . str_replace('&amp;', '&', $return_url) . '";window.close();</script>'; Replace with: echo '<script> if( typeof window.opener === \'undefined\' || window.opener === null ){ window.location.href="' . str_replace('&amp;', '&', $return_url) . '"; }else{ window.opener.location.href="' . str_replace('&amp;', '&', $return_url) . '"; window.close(); } </script>';
  10. This is unrelated, if you haven't requested with PayPal for your client ID to be approved with the scope needed then it wont work anyway. This is just missing an step in the normal setup essentially if this is the reason your "Log In with PayPal" isn't working. The problem I posted is after this stage, either for stores who's client ID's "Log In with PayPal" App's were working or for stores in development using sandbox.
  11. Ok here are the fixes. The fixes have been based on an unmodified default install of osCommerce v2.3.4.1. Backup before making changes, this is provided as is and any changes you make are done so at your own risk (no responsibility accepted here). Unfortunately I don't have available time to help with any customisation but if there are any errors with the code below I'm happy to correct them. First of all in your store admin, make sure Telephone Number and Seamless Checkout is unticked, then save the settings. Note: Possible ongoing problems. Seamless checkout previously allowed users who have logged in via "Log In with PayPal" to continue to make payment without logging in again. As PayPal has removed Seamless as a scope item I'm not sure if customers will have to login again to PayPal once they get to payment method selection or click a Checkout with PayPal button. The new connect/api.js may compensate for this automatically but I haven't tested that far yet so cannot comment either way. In includes/modules/content/login/templates/paypal_login starting line 18 Find: <script type="text/javascript" src="https://www.paypalobjects.com/js/external/api.js"></script> <script type="text/javascript"> paypal.use( ["login"], function(login) { login.render ({ <?php if ( OSCOM_APP_PAYPAL_LOGIN_STATUS == '0' ) { echo ' "authend": "sandbox",'; } if ( OSCOM_APP_PAYPAL_LOGIN_THEME == 'Neutral' ) { echo ' "theme": "neutral",'; } ?> "locale": "<?php echo $cm_paypal_login->_app->getDef('module_login_language_locale'); ?>", "appid": "<?php echo (OSCOM_APP_PAYPAL_LOGIN_STATUS == '1') ? OSCOM_APP_PAYPAL_LOGIN_LIVE_CLIENT_ID : OSCOM_APP_PAYPAL_LOGIN_SANDBOX_CLIENT_ID; ?>", "scopes": "<?php echo implode(' ', $use_scopes); ?>", "containerid": "PayPalLoginButton", "returnurl": "<?php echo str_replace('&amp;', '&', tep_href_link(FILENAME_LOGIN, 'action=paypal_login', 'SSL', false)); ?>" }); }); </script> Replace with: <script type="text/javascript" src="https://www.paypalobjects.com/js/external/connect/api.js"></script> <script type="text/javascript"> paypal.use( ["login"], function(login) { login.render ({ <?php if ( OSCOM_APP_PAYPAL_LOGIN_STATUS == '0' ) { echo ' "authend": "sandbox",'; } if ( OSCOM_APP_PAYPAL_LOGIN_THEME == 'Neutral' ) { echo ' "theme": "neutral",'; } ?> "responseType" : "code id_Token", "locale": "<?php echo $cm_paypal_login->_app->getDef('module_login_language_locale'); ?>", "appid": "<?php echo (OSCOM_APP_PAYPAL_LOGIN_STATUS == '1') ? OSCOM_APP_PAYPAL_LOGIN_LIVE_CLIENT_ID : OSCOM_APP_PAYPAL_LOGIN_SANDBOX_CLIENT_ID; ?>", "scopes": "<?php echo implode(' ', $use_scopes); ?>", "buttonType" : "CWP", "buttonShape" : "rectangle", "buttonSize" : "md", "fullPage" : "false", "containerid": "PayPalLoginButton", "returnurl": "<?php echo str_replace('&', '&', tep_href_link(FILENAME_LOGIN, 'action=paypal_login', 'SSL', false)); ?>" }); }); </script> In includes/modules/content/login/cm_paypal_login.php on line 259 (to prevent a blank/white screen once a user has logged in via PayPal when returning to the store). Find: echo '<script>window.opener.location.href="' . str_replace('&amp;', '&', $return_url) . '";window.close();</script>'; Replace with: echo '<script> if( typeof window.opener === \'undefined\' || window.opener === null ){ window.location.href="' . str_replace('&', '&', $return_url) . '"; }else{ window.opener.location.href="' . str_replace('&', '&', $return_url) . '"; window.close(); } </script>';
  12. I can confirm this is a problem now. I've tested on another store and it does indeed display a white page. I think this is related to Seamless checkout being removed and there's a javascript redirect placed in the <head> tags which doesn't work because it thinks it's in a popup window and not a full page window. I'll provide a fix for this also in a while.
  13. Silly question, but did you click the save button at the bottom of the page after you unticked Telephone and Seamless? I'm working on an updated paypal_login.php content module that uses the new Connect with PayPal API paypalobjects.com/js/external/connect/api.js instead of the old paypalobjects.com/js/external/api.js because if I know PayPal it won't be long before they withdraw that.
  14. UPDATE - NOT DEAD... BUT CHANGES REQUIRED After 3 hours I've discovered what the issue is. PayPal has removed some of the scope items (information about the visitor that is returned back to the store after PayPal login). PayPal no longer provides the following 2 items (tickable within Admin > PayPal App > Configure > Log In ) and if you request it then you'll receive an error message about scope. Telephone Number Seamless Checkout
  15. That doesn't look like the standard Login with PayPal dialogue. Did you click a "Login with PayPal" button for that window to open or did you click "Checkout with PayPal" (Express). The default button "Login with PayPal" button would have been on the login.php page. Although that button would now display "Connect with PayPal" because of the changes PayPal have made today.
  16. PayPal has deprecated the Login with PayPal API and it will no longer work as of this morning, it's officially now Connect with PayPal. PayPal have made changes and all my stores with the service Log In with PayPal no longer work. Also the paypalobjects.com/js/external/api.js script used to generate a html <button> which has now been replaced with a styled <A> tag. I hid this button so I could use my own that and style it how I wanted and used jquery to trigger the hidden button and execute the script. This now fails because it was still looking for a <button> I'm looking into this further now and will try to report back with further news. But if you're wondering why your stores are having less login from this morning or why customers are contacting you saying they can't login, this is why! This has been a long time coming, why isn't there an update for this already for the official Oscom/PayPal app??
  17. Hi Harald, I don't think this is as clear cut as you think. I'm unfortunately suffering from this problem too on a production site and to test it wasn't any addons/customisations I've loaded a brand new 2.3.4 install without any addons/customisations. Please see here http://www.oscommerce.com/forums/topic/409406-oscommerce-bug-brand-new-234-install-without-customisationsaddons/
  18. Hi, Does anyone still require an updated version of the contribution? Pete
  19. Guess it depends on the version of OSC but it's already updated in this contribution http://addons.oscommerce.com/info/7151
  20. Ello, Couple of points. 1: WorldPay Hosted and WorldPay Junior are the same thing (That's marketing for you) . Since the release of the OSC 2.3 WorldPay has changed their payment URLs so the URL's contained in the default WorldPay Modules will need updating. (The official response was "The old URL's may or may not work all the time") From https://select.wp3.rbsworldpay.com/wcc/purchase To https://secure.wp3.rbsworldpay.com/wcc/purchase 2: OSC 2.3 ext/modules/payment/hosted_callback.php still contains deprecated code. Depending on your server it could fail on the very first line of code (line 13) if (isset($HTTP_POST_VARS['M_sid']) && !empty($HTTP_POST_VARS['M_sid'])) { There are compatibility functions within OSC that will check if $HTTP_POST_VARS is valid/supported and if not change them to the new standard $_POST, however the line of code that does this is executed AFTER if (isset($HTTP_POST_VARS['M_sid']) && !empty($HTTP_POST_VARS['M_sid'])) { if (isset($HTTP_POST_VARS['M_sid']) && !empty($HTTP_POST_VARS['M_sid'])) { chdir('../../../../'); require ('includes/application_top.php'); So line 13 (or 1 depending on your perspective) checks to see if M_sid value is set and not empty, if it's set and exists it moves on and on line 15 (or 3) includes application_top.php which will then start the compatibility code conversions. That's not going to help if you continuously fail at line 13 (or 1). So change the above to $_POST. Make sure you have set up different order status for prepairing and successful WorldPay transactions. Check the field (in html source code) of checkout_confirmation.php to make sure the field MC_callback contains a valid return link. Make sure your "Production/Live" configuration in your WorldPay configuration is set up correctly. If your test environment works then just copy the settings from your "Text/Development" WorldPay configuration settings (at the bottom of the page in your WorldPay control panel) to the "Live/Production". Also just so you know if your callback page is being accessed by WorldPay you could insert code to the top of your callback page which will send you an email when it's being accessed with the post values (see below). // Define your debug email address $RBSPostEmail = ''; // e.g $RBSPostEmail = '[email protected]'; $RBSDebugActive = false; //Change to false to disable debug emails. // Build Email $message = "RBS WorldPay Post Values\n".'\n'; foreach($_POST as $name => $value) { $message .= "$name : $value "; } // In case any of our lines are larger than 70 characters, we should use wordwrap() $message = wordwrap($message, 70); if($RBSDebugActive){ // Send Email mail($RBSPostEmail, 'RBS WorldPay Post Values', $message); } Good Luck!
  21. Uploaded updated RBS WorldPay Business Gateway Payment Module (available soon after validation)

  22. Bug fixing AJAX-AttributeManager-V2.8.7 (add/edit options & values OAI). Great idea but very poorly coded and riddled with gremlins!

    1. Juto

      Juto

      I agree :) Just to see the mess set error reporting to -1

      Sara

  23. Hi Mortal, please dont add any more contributions, I'm not sure if you're fully responsible for Ajax Attribute Manager OAI Version but you really shouldn't have posted it in the state its in. No documentation, missing tables and fields, bug ridden all cloaked with error_reporting(0). Please repost fixed or at least warn others not to use it.

  24. Worldpay changed their security policy for response pages. The original that comes with OSC contains Javascript which is no longer permittable by Worldpay and also contains an older style of PHP coding that is no longer supported by new versions of PHP. Sadly it looks like Harald (the creator of OSC and the original Worldpay module) is concentrating his energies somewhere other than OSC as I've reported the original module a couple of times but it's still available to download and still marked as certified when it doesn't work.
  25. Ok Guys, try this. I've added some code to help you debug any issues. Enter your email address in the field below and you'll get sent an email with WorldPay values in it. This is good for two things, 1 to make sure WorldPay is accessing the script (if you dont receive an email then Worldpay cannot access the page) and 2 you can make sure you're recieving the values you need. Give it a go and let me know the results, I'll add it to the package later tonight if it all goes well. <?php /* UPDATED 26-05-2010 Added Debugging Support Via Email Included Meta Refresh Redirect Removed whitespace added by user g_p causing PHP Header/Session Errors Removed unknown post variables added by user g_p ($_POST['hash'] should be $_POST['M_hash']) UPDATED 04-12-2009 Deprecated $HTTP_POST_VARS replaced with $_POST to enable callback on all platforms/php versions. Javascript dependancy for page redirection replaced with form action otherwise Worldpay removes javascript and leaves visitors stranded. Updated By Pete Batin (petebuzzin in Oscommerce forums) Based on Contribution by Harald Ponce de Leon ($Id: junior_callback.php 1807 2008-01-13 00:50:08Z hpdl $) No gaurantees are expressed in anyway, always backup and test before production usage osCommerce, Open Source E-Commerce Solutions http://www.oscommerce.com Released under the GNU General Public License */ // Define your debug email address $RBSPostEmail = '[email protected]'; $RBSDebugActive = true; //Change to false to disable debug emails. // Build Email $message = "RBS WorldPay Post Values\n".'\n'; foreach($_POST as $name => $value) { $message .= "$name : $value "; } // In case any of our lines are larger than 70 characters, we should use wordwrap() $message = wordwrap($message, 70); if($RBSDebugActive){ // Send Email mail($RBSPostEmail, 'RBS WorldPay Post Values', $message); } if (isset($_POST['M_sid']) && !empty($_POST['M_sid'])) { chdir('../../../../'); require ('includes/application_top.php'); if ($_POST['transStatus'] == 'Y') { $pass = false; if (isset($_POST['M_hash']) && !empty($_POST['M_hash']) && ($_POST['M_hash'] == md5($_POST['M_sid'] . $_POST['M_cid'] . $_POST['cartId'] . $_POST['M_lang'] . number_format($_POST['amount'], 2) . MODULE_PAYMENT_WORLDPAY_JUNIOR_MD5_PASSWORD))) { $pass = true; } if (isset($_POST['callbackPW']) && ($_POST['callbackPW'] != MODULE_PAYMENT_WORLDPAY_JUNIOR_CALLBACK_PASSWORD)) { $pass = false; } if (tep_not_null(MODULE_PAYMENT_WORLDPAY_JUNIOR_CALLBACK_PASSWORD) && !isset($_POST['callbackPW'])) { $pass = false; } if ($pass == true) { include('includes/languages/' . basename($_POST['M_lang']) . '/modules/payment/worldpay_junior.php'); $order_query = tep_db_query("select orders_status, currency, currency_value from " . TABLE_ORDERS . " where orders_id = '" . (int)$_POST['cartId'] . "' and customers_id = '" . (int)$_POST['M_cid'] . "'"); if (tep_db_num_rows($order_query) > 0) { $order = tep_db_fetch_array($order_query); if ($order['orders_status'] == MODULE_PAYMENT_WORLDPAY_JUNIOR_PREPARE_ORDER_STATUS_ID) { $order_status_id = (MODULE_PAYMENT_WORLDPAY_JUNIOR_ORDER_STATUS_ID > 0 ? (int)MODULE_PAYMENT_WORLDPAY_JUNIOR_ORDER_STATUS_ID : (int)DEFAULT_ORDERS_STATUS_ID); tep_db_query("update " . TABLE_ORDERS . " set orders_status = '" . $order_status_id . "', last_modified = now() where orders_id = '" . (int)$_POST['cartId'] . "'"); $sql_data_array = array('orders_id' => $_POST['cartId'], 'orders_status_id' => $order_status_id, 'date_added' => 'now()', 'customer_notified' => '0', 'comments' => 'WorldPay: Transaction Verified'); tep_db_perform(TABLE_ORDERS_STATUS_HISTORY, $sql_data_array); if (MODULE_PAYMENT_WORLDPAY_JUNIOR_TESTMODE == 'True') { $sql_data_array = array('orders_id' => $_POST['cartId'], 'orders_status_id' => $order_status_id, 'date_added' => 'now()', 'customer_notified' => '0', 'comments' => MODULE_PAYMENT_WORLDPAY_JUNIOR_TEXT_WARNING_DEMO_MODE); tep_db_perform(TABLE_ORDERS_STATUS_HISTORY, $sql_data_array); } ?> <meta http-equiv="refresh" content="10; url=<?php echo tep_href_link(FILENAME_CHECKOUT_PROCESS, tep_session_name() . '=' . $_POST['M_sid'] . '&hash=' . $_POST['M_hash'], 'SSL', false); ?>"> <style> .pageHeading { font-family: Verdana, Arial, sans-serif; font-size: 20px; font-weight: bold; color: #9a9a9a; } .main { font-family: Verdana, Arial, sans-serif; font-size: 11px; line-height: 1.5; } </style> <p class="pageHeading"><?php echo STORE_NAME; ?></p> <p class="main" align="center"><?php echo MODULE_PAYMENT_WORLDPAY_JUNIOR_TEXT_SUCCESSFUL_TRANSACTION; ?></p> <form action="<?php echo tep_href_link(FILENAME_CHECKOUT_PROCESS, tep_session_name() . '=' . $_POST['M_sid'] . '&hash=' . $_POST['M_hash'], 'SSL', false); ?>" method="post"> <div align="center"> <input name="submit" type="submit" value="<?php echo sprintf(MODULE_PAYMENT_WORLDPAY_JUNIOR_TEXT_CONTINUE_BUTTON, addslashes(STORE_NAME)); ?>" /> </div> </form> <p> </p> <WPDISPLAY ITEM=banner> <?php } } } }else{ include('includes/languages/' . basename($_POST['M_lang']) . '/modules/payment/worldpay_junior.php'); ?> <meta http-equiv="refresh" content="10; url=<?php echo tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $_POST['M_sid'] . '&hash=' . $_POST['M_hash'], 'SSL', false); ?>"> <style> .pageHeading { font-family: Verdana, Arial, sans-serif; font-size: 20px; font-weight: bold; color: #9a9a9a; } .main { font-family: Verdana, Arial, sans-serif; font-size: 11px; line-height: 1.5; } </style> <p align="center" class="pageHeading"><?php echo STORE_NAME; ?></p> <p class="main" align="center"><?php echo MODULE_PAYMENT_WORLDPAY_JUNIOR_TEXT_UNSUCCESSFUL_TRANSACTION;?></p> <form action="<?php echo tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $_POST['M_sid'] . '&hash=' . $_POST['M_hash'], 'SSL', false); ?>" method="post"> <div align="center"> <input name="submit" type="submit" value="<?php echo sprintf(MODULE_PAYMENT_WORLDPAY_JUNIOR_TEXT_CONTINUE_BUTTON, addslashes(STORE_NAME)); ?>" /> </div> </form> <p align="center"> </p> <div align="center"> <WPDISPLAY ITEM=banner> </div> <?php } } ?>
×
×
  • Create New...