What's New
Viewing 8 posts - 1 through 8 (of 8 total)
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic.
I have purchased today your filtering module, but unfortunately it has some issues:
– range slider is not working correctly if values have commas. In example with data values like:
data-values="0,6,6,35,7,8,9,10,11,12,12,7,13,14,15,15,87,16,17,19,19,05,20,21,22,22,22,23,02,24,26,28,28,57,30,32,34,9,34,92,35,37,40,42,44,44,45,47,47,6,47,60,50,50,8,52,53,55,56,58,59,9,62,65,68,72,75,78,80,85,90,95,100,110,115,120,125,130,133,35,140,145,150,160,165,170,175,180,190,210,215,225,240,250,260,280,290,310,360,420"
you can see that 6 is twice there. In fact the other on is 6,35. You need to escape commas if you really on explode function!
– range slider input fields can be enabled only for price and weight. Why not for any attribute that has only numerical values?
At the end I see there that my support has expired even though I have just purchased your module.
Hi,
Sorry, but I do not understand why you need access to the shop itself. Especially it will not tell you much since most of it is in Polish.
Issue is easily reproducible – I am also attaching print screen of my range slider configuration.
Easy filter module
v1.1.0 – z sunnytoo.com
Presta Shop
1.7.6.4
Thanks for reporting the issue and sorry for constantly asking for an access to your site. YOBO isn’t in charge of the range slider feature, he didn’t know the issue could be fixed without accessing to your site to check. We currently work remotely, other wise he would have told me the issue.
I’ve released a new version to fix the issue by using # as the separator, since # is an invalidate character for feature values, there will be no conflicts any more.
We will improve the module next week I guess to make it be possible to use input fields for attributes and features which have only numerical values.
Thanks for reporting the issue and sorry for constantly asking for an access to your site. YOBO isn’t in charge of the range slider feature, he didn’t know the issue could be fixed without accessing to your site to check. We currently work remotely, other wise he would have told me the issue.
I’ve released a new version to fix the issue by using # as the separator, since # is an invalidate character for feature values, there will be no conflicts any more. Upgrade your module to fix the issue, you may need to clear caches to make the fix take effect.
We will improve the module next week I guess to make it be possible to use input fields for attributes and features which have only numerical values.
You must be logged in to reply to this topic.