-
Notifications
You must be signed in to change notification settings - Fork 72
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
Comments
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? |
@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. |
Facing same issue |
@namratavora same module or a different one? |
Facing same issue but model different.
is there any solution??? |
@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. |
Facing exact same issue @dhrumin44 Did someone figure out any solution? |
@Madyo still i can't figure out the issue. if you can find then please share your answer. |
@dhrumin44 updating Amasty module "Improved Layered Navigation" solved the problem for us |
Hi,
Can you help us resolved this issue:
Thanks.
The text was updated successfully, but these errors were encountered: