lat9

Could/would you verify so that I've got a chance of reproducing the issue?

Two queries: ``` SELECT * FROM products_options_stock_attributes WHERE products_id = 3414; SELECT * FROM products_attributes WHERE products_id = 3414; ```

OK, one more dump, please: ``` SELECT * FROM products_options_stock WHERE products_id = 3414; ```

OK, two more ``` SELECT * FROM products_options WHERE products_options_id = 86; SELECT * FROM products_options_values WHERE products_options_values_id IN [418, 419]; ```

... and _finally_ (hopefully): ``` SELECT configuration_key, configuration_value FROM configuration WHERE configuration_key IN ('POSM_OPTIONAL_OPTION_TYPES_LIST', 'POSM_OPTIONAL_OPTION_NAMES_LIST', 'POSM_OPTIONS_TYPES_TO_MANAGE'); ```

Another, because this is just not making sense to me: ``` SELECT DISTINCT pa.options_id, po.products_options_name as options_name, LPAD(po.products_options_sort_order, 11, '0') as sort_order FROM products_options po INNER JOIN products_attributes pa ON...

> It is possible that the `$quotes` array will not have the `methods` key set. For example, in zones shipping if MODULE_SHIPPING_ZONES_SKIPPED is the current zone (see includes/modules/shipping/zones.php line 316)....

> That document says an empty array is acceptable, and this is what's being returned. > > "If no quote(s) is/are available ... the shipping module sets its quotes property...

> That fix didn't make it into 2.1.0. > > As shipped version 2.1.0 of includes/classes/shipping.php has line 262 as > > ``` > if (is_array($quotes)) { > ``` >...

> So, just to confirm ... This only happens when the Zones module has misconfigured settings. So this PR is essentially a duplicate of #6907 ? While the logged warnings...