README

A Magento 2 module that fixes malformed SQL aliases generated by certain extensions (commonly Braintree) in the Admin Sales Order Grid.

Some modules incorrectly construct SQL like:

`main_table`.`main_table`.created_at

which breaks the grid with errors such as:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'main_table.main_table.created_at'

This module cleans the SQL on-the-fly, ensuring your order grid loads correctly.

📦 Installation

Install via Composer:

composer require 0stoya/btfix

Then enable the module:

bin/magento setup:upgrade
bin/magento cache:flush

That's it — no configuration required.

🚀 What This Module Fixes

Magento’s sales_order_grid uses the alias main_table. Some payment/reporting modules incorrectly prepend the alias twice, causing SQL like:

main_table.main_table.status

This module:

1. Hooks into Magento\Sales\Model\ResourceModel\Order\Grid\Collection::load()

2. Inspects the generated SQL (WHERE clause)

3. Detects invalid patterns:

   • `main_table`.`main_table`.field
   • main_table.main_table.field

4. Automatically rewrites them to:

   • `main_table`.field
   • main_table.field

5. Allows the grid to execute normally.

It is safe, upgrade-proof, and does not override core or vendor files.

🛠 Compatibility

✔ Magento 2.3.x ✔ Magento 2.4.x ✔ Fully compatible with Magento 2.4.8-p1 ✔ Works alongside Braintree, PayPal, Adyen, Klarna, custom modules, etc. ✔ No overrides — safe for upgrades

⚙️ Troubleshooting

Still seeing errors?

Some extensions may inject malformed aliases into other SQL parts such as:

• ORDER BY
• HAVING

You can extend the cleaning list inside the plugin:

$partsToClean = ['where', 'order', 'having'];

Other aliases broken?

If another module uses a different alias, simply add another replacement rule.

📄 License

MIT License (or choose another if you prefer).