Post meta field values not showing correctly on WooCommerce Product Categories

Anonymous

#256837

Hi Trevor,

I have this post meta field price_by_metre work correctly on my shop page here – http://dev.wood.websitelove.com.au/shop/ showing -> https://share.getcloudapp.com/Blu5Kwp8

I also have S&F form on my Product Category pages example http://dev.wood.websitelove.com.au/product-category/specials/ however in the post meta field price_by_metre instead of showing the correct min and max it is showing the full shops products min and max instead of the 2 categorised items displayed.

On that page the 2 products have prices $41.88 and $62.83 yet the price range for price by metre says 16 – 106.

Any thoughts on how to get this working

Anonymous

#256838

This reply has been marked as private.

Trevor

#256875

I am sorry, but the range slider min/max do not adjust based on the other filters. This is intentional, as to do otherwise can have unintended consequences.

Read more about this here:

https://support.searchandfilter.com/forums/topic/custom-max-price-for-price-slider/#post-77119

Anonymous

#257009

Reference given is a 404

Trevor

#257013

Most odd, it works for me, but here is the body of that post:

The plugin does not auto update sliders, and the auto detect maximum stays, as you see, on all categories. The way this currently works is intentional.

We do plan to add an option “auto update” or something similar to do what you want, but it’s not yet a feature.

The reason it was implemented this way is because of another use case (following http://demo.designsandcode.com/sfpro-woo-mystile/shop/):

1) Say a user selects price range 10 – 25 (because this is in their budget)
2) Then they select “singles” and get 2 results
3) They realise they no longer want just singles, so they deselect singles.

In your example, after they first select “singles” you are suggesting that the slider “auto update” to 0 - 5 (because the two singles are £2 and £3)… but then once the user deselects the singles, then the price slider is still set to 0 - 5, this is surely not the users intended behaviour.

There are some additional considerations and workarounds that need to be implemented (like returning to the previous set of values), and I will work on an option like you mention, but for now this behaviour is intentional and has been for some time.

I know that this case scenario does not apply in your case, but it is why it is like it is right now. Hope that makes sense.

[Author]

Posts