wakabayashi

@Havouza for such issues there is a new service available: Merchant's Edition The rest is as it was some weeks ago. TB is awaiting its death, if nothing serious changes.

@AndyC I just looked shortly at it. But this is not exactly the same. These are kind of dynamic attributes. In general you could set up the pizza example without the module, you "just" have to generate hundreds of combinations. Or am I wrong?

I am no expert on this. But https://www.w3schools.com/html/html5_audio.asp shows a very simple way to add audio files as html code. You could try to add such a code on product description and see if it works out of the box. Otherwise a clean module with upload function in the BO and display option in the FO wouldn't be very complicated 🙂

From a coding perspective attributes make things more complex 🙂 That's the cheap answer. In general I also don't like it. Not because of virtual products (we don't really use this), but in case of product packs. I seriously ended up to save all my packs as normal products and handle the stock by an own module. But that is something I would like to be changed in the core. It should be possible to use attributes on virtual products and packs. But as you notice, I use a lot of "would like" and "should". If there is not a owner of tb or a new fork, it will never come...

@funnycamel congrats, that's great! Hopefully we can generate a lot more succes stories as yours 🙂

Surely true. Maybe it's still worth to open a github issue with it. On the other hand I wonder, why would someone want to upload a file there and not at the product page?

Checkout the blockcms module...

If you won't/can't sell this product in future I would deactivate this product and make a correct redirect.

Maybe your payment module does send this email!?

Actually by some chance I had to fix own PR today: https://github.com/thirtybees/thirtybees/pull/1026 If this get accepted, my newest version of genzo_category module will again be working 😎

Oh don't blame me for my old comments ^^ In general ASM has it's potential, but quite a lot would have to be fixed or redesigned. But I am still using it on our store... The problem is that, most merchants don't know, how it should be working and then they are not been able (or too lazy) report bugs... That's why this asm project never gets really forward in the core.

Yeah I will fix this sooner or later anyway... But right now I have just so many other things to do...

No idea, which version you are using. This module is broken since a long time as I wanted to make it super clean, but the core ObjectModel doesn't allow it. https://github.com/thirtybees/thirtybees/pull/1026

It works for me without an issue. Are your products set in asm mode? You have set the suppliers too, right?

What does the browser console say?

I believe, thats actually what he was asking for. I don't think he has multiple installation...

I don't know exactly in which cases this files get updated. But I am quite sure, that it updates, when you save url settings. For htaccess you should just add your custom code below that: # ~~end~~ Do not remove this comment, thirty bees will keep automatically the code outside this comment when .htaccess will be generated again

Whatever you mean by "popularity" (?), it wont be easy, I guess.

I just tested like you did: 1. change exchange rate manually 2. call the cron url. It works perfectly here...

Yeah I am using this module. I believe it's working. At least my exchange rates are looking pretty good.

@datakick amazing! This works like charm (with new reviews) 😎

Has anyone also the Smiley Problem? A lot of our customer use smileys on their review and the module seems to output it as "?"... @datakick is there any easy solution for this?

What type do you use in this settings? In the past I had it on "both". But then I noticed, that most user get/answer the html and a few the txt version. Is there any risk if I just chose html? Will the guys, who received txt before, receive html or nothing at all?

Multiple themes would be an overkill in my opinion. We have such little issues quite often. We use just use some {if $shop->id==1} conditions, to solve such things. Not super clean, but works pretty well.

It can happen when the token is outadated/wrong.