wakabayashi

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.

@Chandra I don't think. For what purpose exactly, do you guys need an external ERP System?

When I last time looked at it (maybe two years ago), I concluded that such ERP Systems are oversized for our needs. I decided to modify tb in a way, that it fits us perfect. That's basically what I do on my daily job and it works pretty well. So for my side, there is no (more) an interest in such a connector or whatever 😊

Thanks. But tbh I don't care about this discord, since I can directly contact to the main actors of tb... I will wait and see with what you guys come up 👍

Nope. I said in PN ("what shit is this" about discord). It was enough to immediately get banned 🤣 Well maybe it's not a good idea, to give people power with like 15 forum posts...

Lol I got banned from the discord channel by @AnnaLisik. Ok: then good luck to all of you 😉

I don't have a concrete concept yet. Right now it's more like a poll, to check how big the potential is. I want to see, how many "serious" merchants are we, who would invest 50$ (or more) into this project. A rough idea is like this. We actually still use a crowdfunding project and bring back the feature request, but with incentives. Golden Supporter with at least 50$/month can add features request and vote for feature request. Normal Supporter below 50$/month can vote for feature request. Non supporter will have access to full open source code, but they won't have any influence in the direction of the project. For this to be happen, the pool of golden supporter have to be big enough. So we can hire good devs like (Petr or Markus) for the jobs. That's why I now want to check the potential. This won't be easy at all and won't solve all problems, but maybe it brings some life back. Problems I see: Feature requests vary a lot. Golden Supporters have to "organize" their ideas. Which issues do we all have and which issues are just issues for 1 merchant. Feature requests need to be concrete. It won't be enough to say: "Stock management is bad. Make it better.". The devs need to exactly now, what we expect from them. This voting system / feature request system won't come from god... Feedbacks on the idea are welcome.