Closed owebia closed 5 years ago
After installation of owebia shipping the site cannot be brought back to dev mode.
php 7.1, magento 2.2.2
frontend and backend work fine while in production mode, but will go into infinite loop/infinite loading when the site is switched to developer mode. Things I've tried: cache flushed/cleaned and /generated folder was manually wiped before switch... and more
Now, here's the big kicker... I've tried manually disabling the module(s) via cli with module:disable and then switching to developer. But the site will continue being unresponsive and failing to fully load.
In my case, the only way to fix it was to revert to a previous VM snapshot.
Any ideas?
Hi @dm8mydog Have you runned the setup:di:compile command?
Best Regards,
indeed
tried it again today in a fresh install, the same behaviour occurs. So it's not caused by any other module.
@dm8mydog you SHOULD NOT run setup:di:compile if you are in developer mode
In the original report I mentioned I was in production mode; and that the issues begin after switching to developer mode. I think that's clear :)
edit ignore this part
In my second attempt in a fresh magento2.2.2 install, I did not run compile and I was still in developer mode, the same behaviour occurs with the endless loading, unfortunately there are no clear error messages anywhere to assist in fixing this.
edit ignore that part
I hesitate to try 2.1.7 knowing that I will soon end up in an unsupported environment.
Can it be related to the module configuration? Are you using $quote variable?
I have not reached that point yet since the module causes the site to break.
Hmm, sorry but without any additional clue... You are the first user reporting this issue (this is not the same issue as #33).
shrugs To reproduce all you'd need is a default ubuntu-16.04.3-server-amd64, with a clean magento2.2.2 setup and then follow the instructions provided here .. ie. composer require owebia/magento2-module-advanced-shipping-setting:^2.1.1
This is not a specific conflict with anything on my end.
edited Sorry, I didn't mean to misreport, after everything is all said and done, (the site is switched to production mode, compiled/etc and the module works).... The issue is: You can no longer switch back to developer mode. it will break
A function that is absolutely necessary, for me at least. edited
updated previous comment
Can you try these instructions on switching from production mode to developper mode?
https://amasty.com/knowledge-base/magento-2-modes-set-developer-production-mode
after a 3rd try and a look at your suggestion... it appears it should not matter because according to this: http://devdocs.magento.com/guides/v2.2/howdoi/php/php_clear-dirs.html the directories are automatically cleared when switching deploy modes.
I did try doing that manually to no effect.
I'll re-state the weirdest part of this is that the issue persists even if the module is disabled via the cli. Which is very weird.
I do have a question though, the 2.0.7 version of this module appears to -almost- work on mage2.2.2, it may have broken our checkout page when I was giving it a try (other things were happening so I'm not sure) Could you comment on what would and wouldn't work if v2.0.7 is used on mage2.2.2 ?
Changes since version 2.0.7:
Changes in https://github.com/owebia/magento2-module-advanced-setting-core:
After executing
php bin/magento setup:di:compile
on a store in dev mode, we have a blank page on frontend and a 404 error on backend.