Switch to production mode not possible after upgrade to Magento 2.2.4 #14950
Comments
magento-engcom-team
added
the
Issue: Format is valid
|
Thank you in advance for your help |
|
@achatpc Have you tried to rename the generation folder.? If you don't then I suggest you please try it one and then after try to enable production mode. Hope it'll help. |
|
Hello, Thank you. i try but not work. |
|
Try to set the file permissions again. |
|
Hi, It's not permission issue. I've got the same error on EE 2.2.3 and last amzn/amazon-pay-and-login-magento-2-module v1.2.6. Seems You have to create an issue for mainteiners of the Amazon Paymen extension (https://github.com/amzn/amazon-payments-magento-2-plugin) and ask them about has the module been tested on 2.2.3 and later releases.. |
|
I test this solution but not work. I add issue on: amzn/amazon-payments-magento-2-plugin#220 Thank you |
|
Other symptom is this error when I try to open a product page in developer mode: 1 exception(s): Exception #0 (RuntimeException): Source class "\Magento\Payment\Model\Method\Virtual" for "Magento\Payment\Model\Method\VirtualLogger" generation does not exist. |
|
Deleting the contents of /var/cache/ and /var/page_cache/, then running setup:upgrade and setup:di:compile again fixed this for me. |
|
Thank you. I try this but not work |
|
I am also getting the exact same error and the checkout also breaks because of this critical error. Any input soon would be much appriciated. |
|
I'm also getting the same error. Fresh Install of M2.2.3 last week with a couple 3rd party modules (Codazon_MegaMenu & WeltPixel_OwlCarouselSlider). Upgraded to M2.2.4 this morning and deleted var/cache/*, generated/code, ran setup:upgrade, then setup:di:compile. It errors out on step 4/7 [Interceptors generation]. [RuntimeException] Exception trace: PHP 7.0 |
|
Until the experts at Magento weigh in, I was able to brute force a "fix". Before people inform me this is a dumb idea, I fully understand this is not a real fix but we have a development deadline so I need a temporary solution. So, with that caveat, I hope it helps somebody else if they need a temporary fix. STEP 1: STEP 2: STEP 3: STEP 4: Thanks to @aholovan for the Amazon pay fix! |
|
Hello, Work for my also. But i hope a other solution from Magento |
|
same issue 2.2.4 on compile +1 |
|
same issue 2.2.4 on compile when upgrading from 2.2.3 |
|
Having the same issue, if i try to add a plugin on the LoggerInterface Magento is throwing the same error. If the following snippet is added in the di.xml for example: |
|
Any update on this? Btw when Installing 2.2.4 vanilla it works without compiling errors. In my case the issue occurs after upgrade to 2.2.4 from 2.2.3. |
|
We are having the same issue here after a 2.2.3 to 2.2.4 upgrade, though I have compared to a base install of Magento and it seems to be identical so it may be caused by an extension. |
|
like ksz2013 said , we had welt_pixel plugin to the logger |
|
This issue occurs only when you have a plugin for class "Psr\Log\LoggerInterface" as said by @ksz2013 In our case, it was in WeltPixel's extension app/code/WeltPixel/Backend/etc/di.xml Removing the content solved the problem. The solution of @gclift does work. But modifying so many core files is not worth. Just search your file system for text name="Psr\Log\LoggerInterface" and remove the plugin temporarily until the time we have an official solution. |
|
I updated from Magento 2 CE 2.2.3 to 2.2.4 and had the same issue.
Disabling WeltPixel_OwlCarouselSlider and WeltPixel_Backend worked for me(this module was mentioned in he above posts). Is this a backward incombatible change in 2.24.4 or simply a mistake in the weltpixel module? |
|
Thanks @ravinders-121, good find! We also have the WeltPixel_OwlCarouselSlider. |
|
I think its anything tha plugs into the logger. if you find something that plugs into that with the xml you can potentially just remove the plugin, as it only is making logging better for developers. Why a logger plugin throws this error, I suspect one of the Sales modules may call the logger in some non compatible way. |
|
This is possibly a bug in weltpixel’s extension. Follow this tweet for updates from weltpixel https://twitter.com/_redchamps/status/994258768929095680?s=12 |
|
Hi, For the moment who is using the weltpixel modules, just comment out in the following file: the plugin for the Psr\Log\LoggerInterface (this only disabled the Broken Reference Loggings to the log files) It seems Magento is not allowing at the moment to create a plugin on the LoggerInterface. Workaround for this is implemented and will work in the next releases for the weltpixel modules. |
|
following some comments here i contacted WeltPixel. "We are aware of this issue that came with Magento 2.2.4 , and we already fixed it. The fix will be included in the next products releases next week, after all tests are completed." |
|
we have the same problem. @magento-engcom-team Any updates? |
|
I found a possible source of the problem. |
|
Received response from WeltPixel on the tweet https://twitter.com/_redchamps/status/994258768929095680?s=12 "The new releases are out, all our products are now compatible with Magento 2.2.4" |
|
Ran into the same error message while trying to build a logger that extends Monolog. Problem turned out to be a typo in in di.xml |
ghost
added
the
Component: Bundled Extension
|
We are closing this ticket now, as it seems all of the described errors have no direct relation to the code in this repository and caused by third-party modules. If you believe there is some kind of issue with the core – please create a new ticket describing the problem itself. Thank you. |
Preconditions
Steps to reproduce
Expected result
Actual result
LOG FILE:
The text was updated successfully, but these errors were encountered: