I have integrated chase paymentech module for payment,
It shows perfectly configured in admin side,
But while I try to see it in frontend, It does not show,
What could be the problem?
You didn't mention that you're getting the 'Sorry, we are not accepting payments' error message. That problem is almost always caused by improper Zone setup or payment module configuration which prevents payment from the Zone the customer's address is in.
this one is our testing server. It does not have SSL, but I guess its not the problem of SSL. Because on our live server (Pawprint) there is SSL but its still not working.
As, stevesh mentioned earlier, I think it must be the zone problem. Can you please let me know about it.
<?php
/**
* @package Configuration Settings circa 1.5.0
* @copyright Copyright 2003-2011 Zen Cart Development Team
* @copyright Portions Copyright 2003 osCommerce
* @license <http://www.zen-cart.com/license/2_0.txt> GNU Public License V2.0
* File Built by zc_install on 2012-05-22 11:27:15
*/
/*************** NOTE: This file is similar, but DIFFERENT from the "admin" version of configure.php. ***********/
/*************** The 2 files should be kept separate and not used to overwrite each other. ***********/
// Define the webserver and path parameters
// HTTP_SERVER is your Main webserver: eg-http://www.your_domain.com
// HTTPS_SERVER is your Secure webserver: eg-https://www.your_domain.com
if($_SERVER["HTTP_HOST"]!="localhost")
{
define('HTTP_SERVER', 'http://'.$_SERVER["HTTP_HOST"]);
define('HTTPS_SERVER', 'https://'.$_SERVER["HTTP_HOST"]);
}
else
{
define('HTTP_SERVER', 'http://localhost');
define('HTTPS_SERVER', 'https://localhost');
}
define('DS',DIRECTORY_SEPARATOR);
$dir_path=str_replace("includes".DS."configure.php","",__FILE__);
// Use secure webserver for checkout procedure?
define('ENABLE_SSL', 'true');
// define('ENABLE_SSL', 'false');
// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');
define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_INCLUDES', 'includes/');
define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
define('DIR_WS_DOWNLOAD_PUBLIC', DIR_WS_CATALOG . 'pub/');
define('DIR_WS_TEMPLATES', DIR_WS_INCLUDES . 'templates/');
define('DIR_WS_PHPBB', '/');
// * DIR_FS_* = Filesystem directories (local/physical)
//the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
define('DIR_FS_CATALOG',$dir_path );
//define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
define('DIR_FS_DOWNLOAD',$dir_path.'upload/');
define('DIR_PATH_PRODUCT', $dir_path.'upload/');
define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub'.DS);
define('DIR_WS_UPLOADS', DIR_WS_IMAGES . 'uploads'.DS);
define('DIR_FS_UPLOADS', DIR_FS_CATALOG . DIR_WS_UPLOADS);
define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email'.DS);
// define our database connection
define('DB_TYPE', 'mysql');
define('DB_PREFIX', '');
define('DB_CHARSET', 'utf8');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', 'username');
define('DB_SERVER_PASSWORD', 'password');
define('DB_DATABASE', 'database');
// The next 2 "defines" are for SQL cache support.
// For SQL_CACHE_METHOD, you can select from: none, database, or file
// If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache
// or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
// ie: /path/to/your/webspace/public_html/zen/cache -- leave no trailing slash
define('SQL_CACHE_METHOD', 'none');
define('DIR_FS_SQL_CACHE', $dir_path.'cache');
// EOF
?>
Report Post
Tell staff why this post should be reviewed.
Manage cookie preferences
Our cookie policy has been updated, so we need you to review your preferences and consent again.
