This morning I received a Debug email from Apache alerting me to an issue. These types of alerts are useful as they can flag potential issues. Sometimes they’re critical and sometimes they’re not.
Store Debug Information (Email Alert)
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'amasty_ogrid_weight' in 'order clause', query was: SELECT `main_table`.*, `amasty_ogrid_sales_order`.`base_subtotal` AS `amasty_ogrid_base_subtotal`, `amasty_ogrid_sales_order`.`total_due` AS `amasty_ogrid_total_due`, `amasty_ogrid_sales_order`.`total_paid` AS `amasty_ogrid_total_paid`, `amasty_ogrid_sales_order`.`subtotal` AS `amasty_ogrid_subtotal` FROM `sales_order_grid` AS `main_table` LEFT JOIN `sales_order` AS `amasty_ogrid_sales_order` ON main_table.entity_id = amasty_ogrid_sales_order.entity_id ORDER BY amasty_ogrid_weight DESC LIMIT 200
The phone call…
Moments later, I received an email from an Administrator explaining that he was trying to customise the columns on their Sales Order Grid page - When all of a sudden they received an error and could no longer load the Orders Grid on the backend.
- “Something went wrong with processing the default view and we have restored the filter to its original state” message appeared at the top of the page
- “Attention: Something went wrong” popup displayed
- Then the spinning loading icon kept animating on the center of the screen
- The main menu still worked fine
- All other pages worked fine
- Create New Order button above the Order Grid still worked fine
- No other users were effected
Unfortunately, I didn’t think to take a screenshot at the time.
I’ve no idea what exactly caused the issue and I was unable to recreate in a Development Environment. Based on the Store Debug Email I suspect it may have been related to an Amasty Grid module that is currently installed. However, I can’t back that theory up due to not being able to reproduce it.
In the following post, I’ll explain the process I went through to resolve the error…