Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Magento 2: Error during compilation after upgrading to version 2.2.3

by | May 27, 2021

Magento 2: Error during compilation mostly occur when we run the compile command, setup:di:compile via SSH.

As part of our Server Management Services, we assist our customers with several Magento queries.

Today, let us see how to fix the error during compilation.


Magento 2: Error during compilation

Recently, we had a customer who upgraded to the latest version of Magento 2 i.e. 2.2.3.

However, while he runs the compile command (setup:di:compile) via SSH he comes across the error -:

Errors during compilation:
Incompatible argument type: Required type: \Magento\Framework\View\Layout\Condition\ConditionFactory. Actual type: \Magento\Framework\App\Config\ScopeConfigInterface; File:

Total Errors Count: 1

Error during compilation

While checking we could see that there was a file that we need to remove after the upgrade. This is necessary especially when we upgrade from the old version to the new version (i.e. 2.2.3) because this file doesn’t exist in the latest version.


Instead of copying the files directly on the server, the best way to upgrade to the latest version of Magento 2 is to run:

composer require <product> <version> --no-update
composer update

For the Magento community:

composer require magento/product-community-edition 2.2.3 --no-update
composer update

For Magento enterprise:

composer require magento/product-enterprise-edition 2.2.3 --no-update
composer update

Alternate solution

On the other hand, we came across a support request stating that they were receiving the following error while compilation:

Plugin class Vendor\Module\Plugin\WysiwygConfig doesn’t exist

In this case, we run the below command and set up the upgrade:

php bin/magento setup:upgrade

Then we alter the command to:

php bin/Magento setup:di:compile

Eventually, we cache clean and cache flush.

By doing this, we can know where the error is triggered.

Then, to find the custom/third-party module we need to check the app/code directory.

In the directory, we need to find the line of code: in your app/code directory and post here which file contains this code.

class Vendor\Module\Plugin\WysiwygConfig

Here, since we can confirm it is from the module app/code/Talv/WysiwygFix, we disable it.

To disable the module, we run the below command:

php bin/magento module:disable Talv_WysiwygFix

Another method to disable this module from app/etc/config.php is by changing this module value from 1 to 0.

Then we run the below commands:

php bin/magento setup:di:compile
php bin/magento cache:clean
php bin/magento cache:flush

[Couldn’t fix the error? Feel free to contact us]



In short, we saw how our Support Techs fix the Magento error.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

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

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.