Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with extension https://amasty.com/improved-layered-navigation-for-magento-2.html #38

Closed
dungnv opened this issue Feb 9, 2017 · 9 comments
Labels

Comments

@dungnv
Copy link

dungnv commented Feb 9, 2017

Hi,

Can you help us resolved this issue:

1 exception(s):
Exception #0 (LogicException): Circular dependency: Magento\Catalog\Model\Layer\Category depends on Magento\Catalog\Model\Layer\Category\StateKey and vice versa.

Exception #0 (LogicException): Circular dependency: Magento\Catalog\Model\Layer\Category depends on Magento\Catalog\Model\Layer\Category\StateKey and vice versa.
#0 /vendor/magento/framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\\Catalog...', Array)
#1 /vendor/magento/module-catalog/Model/Layer/Resolver.php(70): Magento\Framework\ObjectManager\ObjectManager->create('Magento\\Catalog...')
#2 /app/code/Amasty/Shopby/Model/Resolver.php(38): Magento\Catalog\Model\Layer\Resolver->get()
#3 /app/code/Amasty/Shopby/Plugin/RouteParamsResolverPlugin.php(30): Amasty\Shopby\Model\Resolver->get()
#4 /vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(93): Amasty\Shopby\Plugin\RouteParamsResolverPlugin->__construct(Object(Magento\Catalog\Model\Layer\Resolver), Object(Amasty\Shopby\Model\Resolver), Object(Magento\Framework\Url\QueryParamsResolver), Object(Amasty\Shopby\Model\Request))
#5 /vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(89): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Amasty\\Shopby\\P...', Array)
#6 /vendor/magento/framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Amasty\\Shopby\\P...')
#7 /vendor/magento/framework/Interception/PluginList/PluginList.php(232): Magento\Framework\ObjectManager\ObjectManager->get('Amasty\\Shopby\\P...')
#8 /vendor/magento/framework/Interception/Chain/Chain.php(65): Magento\Framework\Interception\PluginList\PluginList->getPlugin('Magento\\Framewo...', 'Amasty_Shopby::...')

Thanks.

@msphn
Copy link
Contributor

msphn commented Feb 9, 2017

Hi, I don't have the plugin you mentioned to reproduce this behaviour. This stack trace is just about the Amasty plugin and not about ours.

Did you install the Amasty plugin first or force-login first? Can you maybe try installing them the other way?

@msphn msphn added the question label Feb 9, 2017
@shochdoerfer
Copy link
Member

@dungnv we recently fixed this issue for one of our clients. The source of the problem was found in a theme the client bought. Unfortunately the quality of the theme code was not the best. We were able to fix the problem in the theme. In case you need help, ping me.

@namratavora
Copy link

Facing same issue

@shochdoerfer
Copy link
Member

@namratavora same module or a different one?

@dhrumin44
Copy link

Facing same issue but model different.

Circular dependency: Magento\Framework\View\Layout depends on Amasty\Shopby\Model\Layer\Cms\Manager and vice versa.

is there any solution???

@shochdoerfer
Copy link
Member

@dhrumin44 I don't know this extension, best is to ask the author of the extension to fix this as the error seems to be on their side. We were facing similar issues in the past which badly written themes - themes quickly ported from M1 to M2 with a lot of ObjectManager calls in the template code. Maybe this issue is something similar.

@Madyo
Copy link

Madyo commented Jun 25, 2018

Facing exact same issue @dhrumin44

Did someone figure out any solution?

@dhrumin44
Copy link

@Madyo still i can't figure out the issue. if you can find then please share your answer.

@Madyo
Copy link

Madyo commented Jun 27, 2018

@dhrumin44 updating Amasty module "Improved Layered Navigation" solved the problem for us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants