Place Order button is not working in one page checkout page magento

Place Order button is not working in one page checkout page magento

September 14, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Place Order button is not working in one page checkout page magento

Solving the “Place Order” Button Issue on Magento One Page Checkout

As a senior developer at Laravel Company, I understand the frustration you’re experiencing with your Magento one page checkout not working as expected for guest users. Let’s dive into this issue and find a solution together.

Understanding the Problem

You’ve implemented the Lotus Breath One Step Checkout extension (version 3.2.1) on your Magento 1.9.0.1 installation. While it works perfectly for registered users, there’s an error when trying to place an order as a guest user.

The JavaScript file is throwing a ReferenceError: Review is not defined when the Place Order button is clicked in the one page checkout review step. This suggests that the Review object or function isn’t being properly initialized before it’s used.

Analyzing the Code

Let’s examine the relevant code snippets you provided to understand what might be causing this issue:

Review Totals PHTML File

In your /app/design/frontend/base/default/template/lotusbreath/onestepcheckout/onepage/review/totals.phtml file, we can see that a Review object is being instantiated using the following lines of JavaScript:

<script type="text/javascript">
    //<![CDATA[
    review = new Review();
    //]]>
</script>

This script seems to be properly included within a <script> tag at the end of the file.

Review Info PHTML File

However, looking at your /app/design/frontend/base/default/template/lotusbreath/onestepcheckout/onepage/review/info.phtml file, we notice that this same Review object is being referenced before it’s defined:

<script type="text/javascript">
    //<![CDATA[
    review = new Review();
    //]]>
</script>

This mismatch in script order could be causing the ReferenceError. The Review object is being used before it has been initialized.

Potential Causes and Solutions

Incorrect Script Order

The most likely culprit for this issue is the incorrect order of JavaScript files. Ensure that all the necessary scripts are properly loaded and executed in the correct sequence during the checkout process.

To verify this:

  1. Inspect your page using browser developer tools (like Chrome DevTools or Firefox Developer Tools).
  2. Check the Network tab to see the order in which the JavaScript files are being loaded.
  3. Look for any dependencies between scripts that might be causing conflicts due to incorrect loading order.

Conflicting Extensions

Another possible reason could be conflicts with other extensions you have installed on your Magento site. If multiple extensions use the same global JavaScript objects or functions, it can lead to naming collisions and unexpected errors.

To investigate this:

  1. Temporarily disable all other custom extensions (except for Lotus Breath One Step Checkout) one by one.
  2. Test the checkout process after each extension is disabled to see if the issue persists.

Outdated Extension Version

The Lotus Breath One Step Checkout extension you’re using (version 3.2.1) might have known bugs or compatibility issues with your Magento version (1.9.0.1). It’s always a good practice to keep your extensions up-to-date and compatible with the latest stable Magento versions.

To address this:

  1. Visit the official Lotus Breath website (https://www.lotusbreath.com/) and check if there is an updated version of their one step checkout extension.
  2. If an update is available, make sure it’s compatible with your current Magento version before installing it.
  3. Backup your site data before performing any updates to prevent potential data loss.

Best Practices for Troubleshooting

When dealing with JavaScript errors in Magento:

  1. Always use browser developer tools to inspect the console logs and network requests during the checkout process.
  2. Enable full error reporting in your Magento configuration to get more detailed information about the issue.
  3. Check if there are any related errors or warnings that might provide additional context for the ReferenceError.
  4. Inspect the JavaScript files being loaded across your entire site, not just the one page checkout page.

Conclusion

Based on our analysis of your provided code snippets and considering common issues with Magento extensions, it’s likely that the incorrect script order or conflicts with other extensions are causing the Review object to be referenced before it has been defined.

I recommend carefully inspecting the JavaScript loading sequence and dependencies in your browser developer tools. Additionally, consider temporarily disabling other custom extensions and updating your Lotus Breath One Step Checkout extension if a compatible update is available.

Remember to always keep your Magento installation and extensions up-to-date for optimal performance and security. If you’re still experiencing issues after following these troubleshooting steps, feel free to reach out to our technical support at Laravel Company (https://laravelcompany.com/contact).

Happy coding!

Magento 1 Checkout Extensions Themes

Our network