Daemonj

You will need to modify the flat rate shipping module file to only be active when the cart quantity is set for the desired level.

It is indeed possible but would seriously affect the operation of the store and be fairly difficult to implement and manage.

Every occurrence of FILENAME_ORDERS will need to be changed to FILENAME_ORDERS2 in the orders2.php file.

You need to have a space between "s.orders_status_id" and the word "and". ;) select count(*) as total from orders o left join orders_total ot on (o.orders_id = ot.orders_id), orders_status s where o.orders_status = 1 and o.orders_status = s.orders_status_id and s.language_id = '1' and ot.class = 'ot_total'

Approx. line 259 in the catalog/includes/modules/payment/authorizenet.php file should read: tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, 'error_message=' . urlencode(MODULE_PAYMENT_AUTHORIZENET_TEXT_ERROR_MESSAGE), 'SSL', true, false)); change it to read: tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, 'error_message=' . urlencode($HTTP_POST_VARS['x_response_reason_code'] . '-' . $HTTP_POST_VARS['x_response_reason_text'] . ' ' . MODULE_PAYMENT_AUTHORIZENET_TEXT_ERROR_MESSAGE), 'SSL', true, false)); and the error code and description will be displayed at the top of the checkout_payment page upon the return from authorize.net.

Check the time on your server because if it is off by 3 seconds from Authorize.net's time they will not accept the transaction. You should also edit your catalog/includes/modules/payment/authorizenet.php file to display the return code on an error in the pre_confirmation_check() function. Once you know the error code you can look in the API documentation from Authorize.net to determine the problem and how to correct it.

What is the latest full package install to download?

Access Admin > Tools > Server Information and review the cURL information there to ensure that cURL support is indeed compiled in and you have the correct path.

It looks like the file has been uploaded so what is the problem?

You will have to modify the code and the database. Create a field in the products table to store a shipping option value. Modify the admin/categories.php file to include this new field and then enter the code for the priority mail item. Then edit the catalog/includes/modules/shipping/usps.php file to remove all entries from the results array except for the specified code. If you have multiple shipping options available, you will have to modify the catalog/includes/classes/shipping.php class instead to only return results that match the code specified by the product.

Do you get an error message or what happens? Did you remember to create the temp directory and assign it 777 permissions?

Usually within the support area of the gateway they will have documentation regarding what is necessary to process payments real-time.

Check the contributions area to see if someone has already developed a payment module for the NOVA gateway. If not, then you will need to have one created either by yourself or someone else. Either that or see if your payment processor has access to authorize.net or another gateway that already has a payment module available.

Edit catalog/includes/classes/cc_validation.php and around line 57 should read: return $this->is_valid(); Make is look like: // return $this->is_valid(); return true; and that should do the trick for you. ;)

Just edit the catalog/includes/modules/payment/cc.php file for the changes that you wish.

Use the cc.php or authorizenet.php files as a template to implement the API specific to your payment processor.

When you take into account the monthly fees on top of their charge for a merchant account, that makes PayPal very competitive and sometimes cheaper especially now since they no longer require a user to have an account to pay by Credit Card. Authorize.net is not a merchant account - they are a payment processor. You have to have a merchant account in order to have Authorize.net process your payments. There is a big difference between the two. Using the standard Authorize.net payment module the user is briefly transferred to Authorize.net's site and then returned. This process generally takes 10 seconds are less and the user is rarely aware that it occurred since the page stays blank during that time. It basically looks like the success page takes a while to load. To completely avoid that use the Authorize.net ADC (or AIM) payment contribution which uses cURL to communicate directly with Authorize.net instead of HTTP POST.

oakhill, create a cache (or whatever name you wish to use) folder at the same level as the httpdocs folder and give it 777 permissions. Then set the appropriate path for the file (e.g. /home/httpd/vhosts/[domain]/cache/db_cache.php)

airuma, it sounds like you did not uploade the .sql file that creates the necessary tables.

Delete the file, disable compression, recreate the file, and try that. Do not post your file to the forums.

Is there a blank line in the config_cache.php file though? Not an empty define (e.g. define('MAX_RECORDS', ''); ) but an actual blank line. If so, I will need to modify the contribution to accomodate accordingly.

Yes, it is mainly for the catalog side. Be sure that you have the correct path and filename to the cache file in the catalog/includes/configuration_cache_read.php file. It should be the same as in the admin/includes/configuration_cache_read.php file.

Instead of querying the database for the configuration parameters for every page request by every user, it reads a file containing those parameters.

peego, that should be posted in the general support forum Following are a few suggestions: - do you have GZip compression enabled and set to 1? - have you added any indexes to your database? Search in the Tips & Tricks forum by my name for index and you will find the appropriate article. - if you are running mysql 4 on your server have you enabled query caching? Search in the Tips & Tricks forum by my name for query and you will find the appropriate article. - have you performed a load test on your pages to see what their overall size is?

The script is not able to write to the output file. Verify that the folder that you specified for the cache file's location has 777 permissions.