checkout is not working in magento1.7

checkout is not working in magento1.7

August 10, 2026 · Illustrated author avatarBy Stefan Bogdanescu
checkout is not working in magento1.7

Troubleshooting Magento Checkout Issue: A Comprehensive Guide

Hello everyone, I hope this post finds you well. Today, we’re going to dive into a common issue faced by many developers working with Magento 1.7 - the dreaded checkout not working problem.

The Initial Symptoms & Investigation

The user has reported an issue with a multistore setup in Magento 1.7 where the checkout process is failing for one particular store. More specifically, when clicking the “Continue” button inside the Billing Information block, which typically triggers the billing.save() function, nothing happens.

They’ve checked the response using Firebug and confirmed that all blocks are being rendered correctly. The suspicion lies with the billing.save() function itself - where can we find this function to investigate further?

Digging Deeper: Analyzing the Billing Save Function

The first step is to locate the billing.save() function in your Magento codebase. This function typically resides within the app/code/core/Mage/Checkout/Model/Type/Onepage.php file, around line 740.

Here’s a snippet of the relevant section:

public function saveBilling($data)
{
    // ... (some logic)

    $this->_eventManager->dispatch('checkout_type_onepage_save_billing', array(
        ' billing_address' => $address,
        'model'           => $this
    ));

    return $this;
}

As you can see, this function is responsible for saving the billing information and dispatching an event (checkout_type_onepage_save_billing).

The Response discrepancies

The user has provided the JSON responses they’re receiving from the billing.save() function. For one store (the broken one), a meta tag is being included in the response, which is causing the issue.

This meta tag seems to have been added incorrectly within the index.php file of the subdomain folder. This should never be placed here; it’s likely an error from a previous modification or plugin integration gone wrong.

To resolve this:

  1. Locate and remove the meta tag from your index.php file.
  2. Clear the cache (you can do this via Magento Admin > System > Cache Management).
  3. Try reloading the checkout page to see if the issue persists.

The New Gateway Error & Test Mode

After resolving the meta tag issue, a new problem arises - a gateway error message is displayed when attempting to place an order:

Gateway error: (TESTMODE) The merchant login ID or password is invalid or the account is inactive.

This suggests that there’s an issue with your Authorize.Net payment settings in the broken store. Here are some steps to troubleshoot this:

  1. Double-check your Authorize.Net credentials and ensure they’re correctly configured in the Magento Admin > System > Configuration > Payment Methods section.
  2. Verify that you’ve enabled Test Mode for the correct environment (if applicable).
  3. Check if there’s any conflicting configuration or extension overriding the default settings for the broken store.

Conclusion

In this post, we’ve explored a complex checkout issue in a Magento 1.7 multistore setup and walked through the troubleshooting process step by step. The key takeaways are:

  • Always investigate both frontend (HTML/CSS/JavaScript) and backend (PHP) aspects when dealing with checkout failures.
  • Be mindful of where you’re adding meta tags - never within core files like index.php.
  • Double-check payment method configurations, especially for Authorize.Net or other third-party gateways.

I hope this guide helps you diagnose and resolve similar issues in your Magento projects. If you found this information useful, please consider sharing it with your fellow developers or leaving a comment below.

Remember to check out our Magento Development Services at Laravel Company for professional assistance with complex Magento projects!

Stay tuned for more Magento troubleshooting guides!

Magento 1 Checkout Security Errors

Our network