Yep I have missed that with xampp. Still: like that I can't help. If it were my store I would compare the two version. Check if the html structure is exact the same. If yes I would check css.
It's not about you fixing the bug or something. But how should I understand the problem, if you don't share a link to the issue. I don't have transformer theme...
@Pedalman Yes that is the intention of the module.
@Briljander I am working on a new module for products tags. But I am not yet sure, if and how I will release it.
@danwarrior I will send you the module right now. Would be cool, if you can test it a little.
Ok I have just internally released v.1.1.0. This version fixes the issue of adding a new language and has a much cleaner way of using object model. If you are patreon, I can send you the new version. Just write here in the thread.
Is somebody using this module on his shop? I probably have to release 1.1 soon, as I found an issue, when adding a new language to your store. So if you found any issue or have other improvement suggestion, please place it here 🙂
Is there any issue with the sum of ratings? I just got a review. It's the first of the product. Obiviously it should be 4 stars (as showed also in BO) but the overall Rating is 5 stars: https://www.spielezar.ch/brettspiele/architekten-des-westfrankenreichs
Normally when a customer orders by phone we use a [email protected]. So just a fake email. If the customer really wants his email, to be stored, we use a manual password. Same as you, but we tell the customer that he should use the "Forget password" to set a new one...
I don't know if I have already reported. But there is an issue with criteria that don't apply to all products/categories. In my case I always apply them to categories. But when I edit such a criteria, the categories aren't selected. In addition it says something like: "apply to no product" in the overview.
Yeah I got this. That's why I want to implement the expiration feature. But I really don't get the point having part "expiration". Either it makes no difference at all (when customer doesn't order anymore and lose all it's coins). Or the user loses a part of his coins (in your way) and none coins (in my way). But I as a customer would be totally angry if your case comes in. If I place a new order at your store and still lose some of my coins I would think: Ar they kidding me? I am still buying stuff there, but still delete my coins :S
In addition: how likely is this case? As far as I understand a loyalty points system almost always works like this: You order something and collect a few points. You use them on your next order and the thing is done. Doesn't 99% of the orders work like this?
Probably the module doesn't show it. But I get your point. There is nothing wrong in adding this number somewhere 😉
Tbh: that would be quite a huge rewrite/extension. And I really don't believe it's user friendly.
If somebody is interested to code this solution, I am open for merging something. But I won't code this "feature" myself.
When I am looking again deeper at the module I will think, if I can implement a solution for customer returns.