X-Cart forums

[vladimir.gritsenko]

Originally Posted by not_so_young_greg

There is something I do not quite understand about this module: It is said it works with product variants but does it?

Lets create a product that has option class "size" populated with S,M,L. Now lets make it as variants and put 0 in size S - (somebody has just bought your last S). X-cart shows S properly as "out of stock". But one can still filter by size S and get this product listed, even if "in stock only" checkbox is checked.

It does not make much sense for me - I believe if a customer wants to find size S, he should get products that have S available, especially with "in stock only" checked. He filters for S that is in stock, right? Or am I missing something?

Thanks for noticing it. Actually, this is a tricky issue. Let me try to explain.

Imagine there are two classes with two options each, combined in four variants. For example,

Color: Red, Green
Size: S, L

the resulting variants are:

Red S
Red L
Green S
Green L

Now, let's say "Red S" variant is out of stock. How in this case should the filtering behave? In fact, there is no problem if the filters selection is as follows:

Color: Red
Size: S

In this case we can disable "In stock only" filter but what if it's chosen like:

Color: [not selected]
Size: S

or

Color: Red, Green
Size: S

Should it disable "In stock only" filter in these particular cases? It's a hard question, isn't it?

This is a very basic variants example. Imagine, there are 10 classes with 10 options each. A customer will have to choose one and only one attribute from each variants-related filter to have "In stock only" react basing on variants stock levels.

Nevertheless, I've registered this in our bugtracker - we will think what can be done here. Your suggestions will be much appreciated.

Thank you.

[vladimir.gritsenko]

Originally Posted by ADDISON

A very important issue is related to Price min-max inputs. Refine Filters should work with X-MultiCurrency. For the moment it is not working.

If you set up 3 currencies, first time you will see $ in price range. But if you change front-end currency to Euro, price ranges remain in USD. Normally if you change the currency, the values in price ranges should change according, from minimum price to the maxim one.

Personally I get rid of symbol $ near input boxes (imagine some currencies are not just one symbol, but letter. But I will update in Filter name, just after Price, inside round brackets, the currency, based also on Front-end currency (e.g. Price (Euro), Price ($), Price ($). In this way it is a clean design, intuitive, which not consuming space (inserting for example USD near input boxes, will brake the layout, imagine how annoying is when changing currencies).

I've registered this bug. We hadn't have a chance to check the compatibility with all paid add-ons before the release.

[vladimir.gritsenko]

Originally Posted by ADDISON

>> There is an issue with Assigning product class in product management page. I created before a filter class named Fabric, I would like to assign it, but after I push [Apply] still Undefined, even the filter class is in selector.

This is something strange. It works fine at our installations. I suggest you to post a support ticket to helpdesk. Please make sure we have an up-to-date access to your server.

[not_so_young_greg]

Originally Posted by vladimir.gritsenko

Thanks for noticing it. Actually, this is a tricky issue. Let me try to explain.

Imagine there are two classes with two options each, combined in four variants. For example,

Color: Red, Green
Size: S, L

the resulting variants are:

Red S
Red L
Green S
Green L


Now, let's say "Red S" variant is out of stock. How in this case should the filtering behave? In fact, there is no problem if the filters selection is as follows:

Color: Red
Size: S

Yes. In this case if "in stock only" is checked it should show nothing. If is unchecked,should show Red S

Originally Posted by vladimir.gritsenko

In this case we can disable "In stock only" filter but what if it's chosen like:

Color: [not selected]
Size: S

or

Color: Red, Green
Size: S

Should it disable "In stock only" filter in these particular cases? It's a hard question, isn't it?

In my opinion: In your first example color: [not selected] it should show Red S and Green S, if "only in stock" is unchecked. Otherwise should show only Green S.
If a customer wants Red and Green in size S (quite common I think), the filter should behave alike: if "in stock only" is checked, shows Green S (Red S is out of stock), otherwise shows both items.

Originally Posted by vladimir.gritsenko

This is a very basic variants example. Imagine, there are 10 classes with 10 options each. A customer will have to choose one and only one attribute from each variants-related filter to have "In stock only" react basing on variants stock levels.

I perfectly know from my experience that variants are confusing and power-consuming.
But what is actually funny is that every filter I have had a look at, had "filter by size" option, obviously designed for apparel stores. And they were all based on option classes, disregarding availability.
But we all know that when a clothing store owner buys a jacket, he buys sizes S,M,L,XL,XXL etc., at least in most cases. And soon he ends up with only L in stock, the thing cannot be reordered because it is last fall collection and so on.

In a case like this filtering by size is useless since most items have all the sizes. If a customer searches for size L, he definitely should have an option "show only what is in stock".
Otherwise this filter is good only for people who search for a quadruple L or XXS - sizes that are not so common.
And adding "in stock only" filter is only confusing because apparently it does not filer by availability.

By the way: what is this filter for? To show in-stock items when "show out of stock items" is checked in apperance settings?

But thanks for your answer. I know you guys will come up with a good solution soon.

[ADDISON]

Did you check your public demo? In my case it has the same issue.

Originally Posted by vladimir.gritsenko

This is something strange. It works fine at our installations. I suggest you to post a support ticket to helpdesk. Please make sure we have an up-to-date access to your server.

[RoeBoeDog]

Hello Thanks for the great module.

I love how it can pick up your variants however I have found a issue I can not solve.

Example

I sell some motorcycle helmets and we have the following sizes
S
XS
M
L
XL
XXL

When the variants display on the filter page it displays them in ABC order I need them to display from S to XXl

How do you set the positions to display on items you need NOT by ABC


Thanks

[Online Michael]

I'm guessing this module won't be available for 4.4.X ?

[vladimir.gritsenko]

Originally Posted by not_so_young_greg

But thanks for your answer. I know you guys will come up with a good solution soon.

Sure, we will do our best to find the best solution. Thank you.

[vladimir.gritsenko]

Originally Posted by ADDISON

Did you check your public demo? In my case it has the same issue.

It's even more strange now We will take a look what the problem is.

[vladimir.gritsenko]

Originally Posted by RoeBoeDog

Hello Thanks for the great module.

I love how it can pick up your variants however I have found a issue I can not solve.

Example

I sell some motorcycle helmets and we have the following sizes
S
XS
M
L
XL
XXL

When the variants display on the filter page it displays them in ABC order I need them to display from S to XXl

How do you set the positions to display on items you need NOT by ABC

For now, it's not possible to sort attributes and we now realize that it is a problem. ADDISON already pointed this issue out so we planned to implement the sorting ability. It will be included into the module soon.