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

Wrong filter Values in category #3950

Closed
rockgold22 opened this issue Sep 19, 2020 · 6 comments
Closed

Wrong filter Values in category #3950

rockgold22 opened this issue Sep 19, 2020 · 6 comments
Assignees
Labels
Bug Fixed When bug issue is fixed. Bug Something isn't working.

Comments

@rockgold22
Copy link

Bug report

Wrong Filter Values(Brand attribute) in categories

Even if a particular brand is not selected for a category it is shown on that category filter.

Issue Description

Create a brand value from the admin panel and associate it with a category but this brand will also be shown in all the other categories filter where it is not associated. e.g if I created a brand value as condom brand name like(skore,durex. etc) it is showing in the condoms filter which is correct but it is showing in the filter of sanitary pads categoriy even without association which is absolutely wrong

Preconditions

Please provide detailed information about your environment as possible.

1. framework Version I am using is 1.2.0.
2. Commit id.

Steps to reproduce

Create a brand value from the admin panel and associate them with any desired category and channel

Expected result

It must shown on filters with associated categories only

Actual result

Instead it is showing on every single category whether it is associated with this attribute value or not. To support my argument please find the screenshot of the category where these attribute values are not associated.
bagisto_filter_issue

@rockgold22
Copy link
Author

@jyoti-webkul @shubhwebkul @asif-webkul @bhanu-webkul Any help will be appreciated.

@vaishaliwebkul vaishaliwebkul added the Bug Something isn't working. label Sep 19, 2020
@vishal-webkul vishal-webkul self-assigned this Sep 23, 2020
vishal-webkul added a commit to vishal-webkul/bagisto that referenced this issue Sep 24, 2020
@vishal-webkul vishal-webkul self-assigned this Oct 6, 2020
vishal-webkul added a commit to vishal-webkul/bagisto that referenced this issue Oct 7, 2020
@jitendra-webkul jitendra-webkul added the Bug Fixed When bug issue is fixed. label Oct 8, 2020
@vaishaliwebkul
Copy link

@rockgold22
please check now, this is resolved in the master branch.

So closing this, feel free to reopen anytime if still exist.

@rockgold22
Copy link
Author

rockgold22 commented Oct 17, 2020

@vaishaliwebkul how will i get in my existing website , in past you have told me to upgrade my composer.json to latest version but i already have 1.2.0[APP Version] and bagisto version 1.1.2(which is the latest version itself) so to what version i have to upgrade my composer.json. I have downloaded the bagisto via composer.

@rahulanand77
Copy link

Hi @vaishaliwebkul , I have upgraded my bagisto version to the latest as per the documentation. Surprise, I am seeing new error on the front end as well as in the backend. Can you quickly check and let us know the solution to this issue?

image

image

@rockgold22
Copy link
Author

hi, @vaishaliwebkul can you please help with the above issue faced by @rahulanand77 since I am also facing the same issue after updating my existing site on the localhost.

@vaishaliwebkul
Copy link

@rahulanand77 @rockgold22
it seems the migration command is not executed successfully so you both are getting this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Fixed When bug issue is fixed. Bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

5 participants