Today, immediately after 2.2 official release we decided to update one of the in development project hoping to fix some ongoing issues.

Our stack behind the store was:

– Some Amasty plugins
– Elasticsearch
– Custom theme developed on less preprocessor

Problems spotted and solved:

		Incompatible argument type: Required type: \Magento\Framework\DB\Adapter\AdapterInterface. Actual type: \Magento\Framework\Model\ResourceModel\Db\AbstractDb; File

Update your Amasty modules to newest edition, they have Magento 2.2 support already included

Exception #0 (Exception): Notice: Undefined variable: imageBlockBuilder in /var/www/emilebakker/app/design/frontend/Emile/bakker/Magento_Catalog/templates/product/list.phtml on line 53

Some of the theme overwritten templates can be out of date. There’s no other option then to fix them manually adjusting code with vendor usage.

Errors during compilation:
		Incompatible argument type: Required type: \Magento\Contact\Model\ConfigInterface. Actual type: \Magento\Framework\Mail\Template\TransportBuilder; File: 

Changes are related to custom plugins as well, spending some time for adjusting Dependency Injections and methods.

Compilation from source: /home/eb/domains/
variable @copyright__background-color is undefined in file /home/eb/domains/ in _module.less on line 438, column 40
436|     body {
437|         .ie9 & {
438|             .lib-css(background-color, @copyright__background-color);
439|         }
440|     }
441|  in _responsive.less

Remove your var/view_preprocessed dir and let it rebuild. If the problem would persist and you are in hurry try to remove all @copyright__background-color references in vendor (like vendor/magento/theme-frontend-luma/Magento_Theme/web/css/source/_module.less.

Magento 2.2 seems to be bit faster and less buggy out of the box. I regret only that nobody could say the release date on last Meet Magento conference we’ve attended in Krakow speaking only ‘soon’ like year ago. Well, good job anyway that solved lot of bugs well known for months not officially solved until today such as MAGETWO-60602

Don’t forget to check if new Magento 2 folder /generated containing generated di classes is gitignored and would not be pushed to your code source repository

Leave a Reply

Your email address will not be published. Required fields are marked *

Fork us on GitHub