Jump to content



Member Since 19 Mar 2009
Offline Last Active Oct 04 2018 04:15 PM

Topics I've Started

Credit Card Responce 403

15 March 2017 - 08:14 PM

I have started getting failed credit card from orders.  we are on a cs-cart ver 2.1.1 and  use sage payment solutions for processing.  orders show failed. I have copied cc transaction log file.  Looks to me that I am getting a web page as a response.

merchant id and key have been changed here. 


Any thoughts why this is happening?





URL: https://va.eftsecure...dll?transaction
Request: 'M_id=12345&M_key=123456&T_code=01&T_ordernum=40408&T_amt=2.92&C_name=******&C_cardnumber=******&C_exp=******&C_address=2440%20State%20St.&C_city=Granite%20City&C_state=Illinois&C_country=United%20States&C_zip=62040&C_cvv=990'
Response: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR...l1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> <title>403 - Forbidden: Access is denied.</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;} fieldset{padding:0 15px 10px 15px;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;} #header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF; background-color:#555555;} #content{margin:0 0 0 2%;position:relative;} .content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} --> </style> </head> <body> <div id="header"><h1>Server Error</h1></div> <div id="content"> <div class="content-container"><fieldset> <h2>403 - Forbidden: Access is denied.</h2> <h3>You do not have permission to view this directory or page using the credentials that you supplied.</h3> </fieldset></div> </div> </body> </html>




Radiogroup Change Default

14 February 2017 - 01:59 PM

I am still using cs-cart 2.1.1.  Years ago i set up a user profile field asking if they would like our newsletter with a simple radiogroup.  with a  yes or no radio.  It automaticly defaulted to yes.  At that time I thought this would be fine.   Years later I have found that this is not the best practice of adding to our newsletter.  I would like the default to be no, so they will have to opt in.  How should I do this, and keep the answers in same order.   I believe I have found the correct file to edit, just not sure of code changes. 

File: /skins/new_vision_blue/customer/views/profiles/components/profile_fields.tpl


Code to change, I think:


{elseif $field.field_type == "R"}  {* Radiogroup *}
  {foreach from=$field.values key=k item=v name="rfe"}
  <input class="radio valign {$_class}" type="radio" id="{$id_prefix}elm_{$field.field_id}_{$k}" name="{$data_name}[{$data_id}]" value="{$k}" {if (!$value && $smarty.foreach.rfe.first) || $value == $k}checked="checked"{/if} {$disabled_param} /><span class="radio">{$v}</span>



Thanks for your help,

David DeWitt




Usps Dropping Support For Sslv3

15 November 2016 - 07:01 PM

I received the following message from USPS. What will I need to do to make sure we have no issues with getting shipping cost to our web site.  We are using cs-cart ver2.1.1
Thanks for any help,
David DeWitt

This message explains some security improvements planned for our services. Effective March 2017 (exact date to be determined), Web Tools will discontinue support of SSLv3 for securing connections to our HTTPS APIs including all shipping label and package pickup APIs. After this change, integrations leveraging SSLv3 will fail when attempting to access the APIs.

You are receiving this message because the Web Tools UserID associated with your email address has made HTTPS requests over the past year. It is possible that no changes are necessary to retain Web Tools services and benefit from the improvements. Please review the entire message carefully and share with your web developer, software vendor or IT service provider to determine if your use of the Web Tools APIs will be affected.If you have already updated your security certificates please disregard this message. If you are not sure if any changes are necessary, please ask your IT service provider.


Background: Security research published in recent years demonstrated that SSLv3 contained weaknesses that limited its ability to protect and secure communications. These weaknesses have been addressed in the replacement for SSL, Transport Layer Security (TLS). Since then, major browser software vendors have been disabling support for SSLv3 and their work is largely complete. Consistent with our priority to protect USPS Web Tools customers, Web Tools will only support versions of the more modern TLS rather than SSLv3.

Contact us at WebTools@usps.gov with any questions or concerns.