Circular dependency Error
photolink opened this issue · comments
We have recently had the LiteMage extension installed by our hosting company however the following error is showing:
Circular dependency: Litespeed\Litemage\Model\CacheControl depends on Litespeed\Litemage\Observer\FlushCacheByTags and vice versa.
Has anyone seen this or have a fix for it?
Steps taken:
- Extension installed
- Extension Enabled
- Setup:Upgrade run
- Static files deployed
Is this happened when you try to upgrade your theme? Or just try to enable LiteMage extension?
We have only tested it by taking all the steps mentioned above. The host (Simple Servers) did other checks and were not able to get it working.
The site is on Magento CE 2.1.0.
@photolink Did you re-compile ?
Extension installed
Extension Enabled
Setup:Upgrade run
setup:di:compile
setup:static-content:deploy
cache:clean
No we have not compiled the site as yet. After the upgrade process we just deployed the static content.
If you are running in default or production mode you really need to run the compile command.
You can check by deploy:mode:show
@photolink I am using the same host with litemage without problems. That said their support guys are pretty limited in my experience until you get to third tier. I'm using magento 2.1.3 and litemage 2.0.4
Definitely try compiling as @rkhoury82 suggests. The dependency injection stuff gets set up then, which is what it is complaining about. Magento always tells me to compile after a setup:upgrade anyway.
@photolink I put some new updates, have not labeled to release 2.0.5. Can you test it and confirm if the error goes away?
I tagged release 2.0.5. I believe your issue should be fixed. Please confirm.
Thanks - the new version has worked to the extent that the site is running and i was able to select LiteMage as the FPC caching option; however, when checking the response header, i am not seeing the expected value.
For reference the site is http://devm2.opumo.com
If you see the page is not cached, means that url is not cacheable. If you switch to built-in cache, it will also not cached. You need to find out from the layout file which block caused that. If you email to info@litespeedtech.com to request adding to slack team, I can help you trouble shoot there.
The issue is now sorted following the 2.0.5 update and removing some cache blocking code. Thanks Lauren for your assistance.