[BUG] Attributes are displayed incorrectly (broken)!
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from laura on July 5, 2021, 10:40Hello,
I bought your plugin only so that we can use product attributes as slider.
Unfortunately, we found that many of our attributes seem to be misinterpreted.
So the following:Where it works for example are attributes with the following content:
103/804 kWh, 113/762 kWh, 129/754 kWh, 129/934 kWh, 134/906 kWh, 136/1.133 kWh
so far so good!But the following attributes are displayed incorrectly:
12.0 (1.5~13.5) kW, 13.5 (1.5~14.0) kW, 2.5 (0.8~5.3) kW, 2.7 (0.8~5.5) kW, 2.7 (0.9~4.2) kW, 2.7 (0.9~4.3) kW
Here the attributes are split as follows, ONLY THE FIRST VALUE "12.0 (1.5~13.5) kW":
"12", "0(1", "1~13", "5) kw".And that for every single attribute that is similar in structure.
This must be a bug, because actually the plugin should not split the individual "fields" or the attributes and interpret them that way, but process them as a whole.
It should take the first interpretable value (in this case "12,0") into the calculation for the sorting.
Please fix, because otherwise the plugin has no purpose for us, since almost all our attributes are shown broken.
Hello,
I bought your plugin only so that we can use product attributes as slider.
Unfortunately, we found that many of our attributes seem to be misinterpreted.
So the following:
Where it works for example are attributes with the following content:
103/804 kWh, 113/762 kWh, 129/754 kWh, 129/934 kWh, 134/906 kWh, 136/1.133 kWh
so far so good!
But the following attributes are displayed incorrectly:
12.0 (1.5~13.5) kW, 13.5 (1.5~14.0) kW, 2.5 (0.8~5.3) kW, 2.7 (0.8~5.5) kW, 2.7 (0.9~4.2) kW, 2.7 (0.9~4.3) kW
Here the attributes are split as follows, ONLY THE FIRST VALUE"12.0 (1.5~13.5) kW":
"12","0(1","1~13","5) kw".
And that for every single attribute that is similar in structure.
This must be a bug, because actually the plugin should not split the individual"fields" or the attributes and interpret them that way, but process them as a whole.
It should take the first interpretable value (in this case"12,0") into the calculation for the sorting.
Please fix, because otherwise the plugin has no purpose for us, since almost all our attributes are shown broken.
Quote from Pablo Borysenco on July 5, 2021, 15:07Hello
Please paste your license key here - https://share.pluginus.net/image/i20210618130558.png -> https://share.pluginus.net/image/i20210618130614.png and wp-admin access - https://share.pluginus.net/image/i20210618130637.png
Drop me exact link to the issue
Hello
Please paste your license key here - https://share.pluginus.net/image/i20210618130558.png -> https://share.pluginus.net/image/i20210618130614.png and wp-admin access - https://share.pluginus.net/image/i20210618130637.png
Drop me exact link to the issue
Quote from laura on July 7, 2021, 16:04Hello Pablo,
ive added the infos you wanted.
Hello Pablo,
ive added the infos you wanted.
Quote from Pablo Borysenco on July 8, 2021, 11:44Hello
Ok! Can you use the point instead a comma ( as you provided in the example - https://share.pluginus.net/image/i20210708123648.png )
your attributes - https://share.pluginus.net/image/i20210708123756.png
An example - https://c2n.me/4cDcsxL.mp4
Hello
Ok! Can you use the point instead a comma ( as you provided in the example - https://share.pluginus.net/image/i20210708123648.png )
your attributes - https://share.pluginus.net/image/i20210708123756.png
An example - https://c2n.me/4cDcsxL.mp4
Quote from laura on July 8, 2021, 15:46I'm not allowed to do that, because in Germany it is a convention to use that in this form :(
What else can I do ? :(
I'm not allowed to do that, because in Germany it is a convention to use that in this form :(
What else can I do ? :(
Quote from Pablo Borysenco on July 9, 2021, 16:47Hello
Ok! Please drop me FTP access - https://share.pluginus.net/image/i20210618130558.png ->https://share.pluginus.net/image/i20210618130637.png - I will fix it
Hello
Ok! Please drop me FTP access - https://share.pluginus.net/image/i20210618130558.png ->https://share.pluginus.net/image/i20210618130637.png - I will fix it
Quote from laura on July 10, 2021, 11:35Hello Pablo,
thank you very much, it seems you already have a solution :)
Unfortunately, we have had bad experiences in the past with giving access to third parties, where someone actually tried to upload virus infected files on the stage server.
So our company is careful not to grant FTP access anymore.
It would be fine for us if you share the fix code and tell us where to paste it.
We have programmers in the team, but not PHP developers, but they will be able to integrate it correctly.In general, I think that surely others have a bug with the formatting (whether they see it or not, the source of the bug is there), and that it could be interesting for others as well, so I think that a plugin update with the fix would be a good thing for others as well.
I would be very grateful if we could get the code in advance and embed it so we can package the plugin on the live server :)
Thanks a lot for your work and your cool plugin.
Best regards,
Laura
Hello Pablo,
thank you very much, it seems you already have a solution :)
Unfortunately, we have had bad experiences in the past with giving access to third parties, where someone actually tried to upload virus infected files on the stage server.
So our company is careful not to grant FTP access anymore.
It would be fine for us if you share the fix code and tell us where to paste it.
We have programmers in the team, but not PHP developers, but they will be able to integrate it correctly.
In general, I think that surely others have a bug with the formatting (whether they see it or not, the source of the bug is there), and that it could be interesting for others as well, so I think that a plugin update with the fix would be a good thing for others as well.
I would be very grateful if we could get the code in advance and embed it so we can package the plugin on the live server :)
Thanks a lot for your work and your cool plugin.
Best regards,
Laura
Quote from Pablo Borysenco on July 12, 2021, 16:50Hello Laura
Try in file - wp-content\plugins\woocommerce-products-filter\ext\slider\views\woof.php - change code - https://share.pluginus.net/image/i20210712174747.png
and in file - \wp-content\plugins\woocommerce-products-filter\ext\slider\js\html_types\slider.js - change code - https://share.pluginus.net/image/i20210712174923.png
clear all cache and do a test
Hello Laura
Try in file - wp-content\plugins\woocommerce-products-filter\ext\slider\views\woof.php - change code - https://share.pluginus.net/image/i20210712174747.png
and in file - \wp-content\plugins\woocommerce-products-filter\ext\slider\js\html_types\slider.js - change code - https://share.pluginus.net/image/i20210712174923.png
clear all cache and do a test
Quote from laura on July 12, 2021, 20:51Thanks for that.
Your first suggestion would have meant that we would have had to change all the attributes and then probably reassign them all. That probably would have taken us several days.
Your suggestion to change the attributes was absolutely misleading. People buy a plugin because of a feature and the support that is supposed to help their product work for the customer. And not the other way around, isn't it?
I also don't understand why it is so dominant in the WordPress scene to want to get rights everywhere, to get FTP access and to give out code only on explicit request?
Whatever, so it went in just a few seconds, instead of a few days and to pay employees for it. So I really appreciate your help.
Thanks for that.
Your first suggestion would have meant that we would have had to change all the attributes and then probably reassign them all. That probably would have taken us several days.
Your suggestion to change the attributes was absolutely misleading. People buy a plugin because of a feature and the support that is supposed to help their product work for the customer. And not the other way around, isn't it?
I also don't understand why it is so dominant in the WordPress scene to want to get rights everywhere, to get FTP access and to give out code only on explicit request?
Whatever, so it went in just a few seconds, instead of a few days and to pay employees for it. So I really appreciate your help.
Quote from Pablo Borysenco on July 13, 2021, 13:16Hello
That probably would have taken us several days. - you need to change only in the attribute edit page. And it will take several days only if you have several thousand attributes.
to get FTP access and to give out code only on explicit request? - Because most users are not programmers and cannot change the code.
Welcome;)
Hello
That probably would have taken us several days. - you need to change only in the attribute edit page. And it will take several days only if you have several thousand attributes.
to get FTP access and to give out code only on explicit request? - Because most users are not programmers and cannot change the code.
Welcome;)