wakabayashi

I dont understand the problem, tbh. You can not add the hook under "positions" or what?

@30knees said in Error messages when adding orders from the backend: "An order has already been placed with this cart. This product cannot be added to the cart." We get this one too! No idea when it happens and why :(

@mauroagr Ah yeah I think I see the problem: @Traumflug doesn't the $this->tplviewvars just get overriden, when you call parent::renderView()?

What is not working? Do you get any error or is the variable just not accessible? How does your override class look like?

Great work @Traumflug, @lesley and @datakick

@rubben1985 said in 19 Patron ?!: @wakabayashi said in 19 Patron ?!: At least ASM is full of bugs and bad design. I coded an own ERP module, otherwise I couldn't continue our store with TB. Any place where I can see the module in action? Do you sell it? a good ERP is one of the parts that I did not find for PS or TB (not in a affordable way) No sorry, that can't be an official module. It was completly devlopped for our own needs. We use own bundles and stuff. If I could have used the core bundles, I would have thought about it, but like that, it makes no sense at all.

@doclucas said in 19 Patron ?!: Fast Forward 9-10 months: @wakabayashi said in 19 Patron ?!: Somtimes I have the feeling, that some features aren't even used by any other merchants than us. In advanced stock management and multistore there are so many bugs, that active merchants would (have to) report. Recently I tried to use the mailchimp module. Unfortunately it's not working (with multistore). How can it be, that Michael invest a lot of time in developing and we (merchants) don't even have time, to test and give feedbacks? For the crowdfunding elasticsearch module I see similair problems. Look at it: https://github.com/thirtybees/elasticsearch/issues?utf8=%E2%9C%93&q=is%3Aissue Almost no feedback by merchants... I know that there are a few feedbacks in the forum, but that is by far not enough. One of the issues I personally noticed with at least some of your bug reports is that they are very hard to reproduce (by me at least). I tried to look into it and wasn't able to. I asked you to write the full steps to reproduce on the latest TB, but still no response. I responded you!? This issue was written 1 year ago. This isn't a serious issue compared to my other reports. Yeah they are hard to reproduce, since we are using the system in a hardcore way. Multistore and ASM. At least ASM is full of bugs and bad design. I coded an own ERP module, otherwise I couldn't continue our store with TB.

@Galloper What are you talking about? This forum has nothing to do with PS 1.6.20.1

In the footer it says 2006-2017...

The proper way to change list, is using hooks: https://webkul.com/blog/how-to-modify-fields-list-in-prestashop/

Yes you are right: multistore is the thing to use. To your concret problem: did you check cache?

@doclucas said in prozis.com I think is a great example: @wakabayashi said in prozis.com I think is a great example: Sure it is. But I don't like the idea, that every module includes it's own technique. :) Imagine you include this one to your module. Another coder adds another editor to his newsletter module. That is in my opinion not a nice situation for the merchants. Maybe I don't understand this argument so well, but what exactly do you propose? You can load tinymce with one line of code to your textarea (backoffice). Something similair for a pagebuilder would be nice.

Sure it is. But I don't like the idea, that every module includes it's own technique. :) Imagine you include this one to your module. Another coder adds another editor to his newsletter module. That is in my opinion not a nice situation for the merchants.

I know, but not a good one :) It also not what I would call a modern landing page builder. I mean something like that: https://grapesjs.com/demo.html

Thats the module I bought some years ago. It's horrible. :)

You can also code a module ofc. But from my opinion, tb anyway needs a landing page builder... Once you do this as a module, you will see in the feedback how flexible that thing has to be... Some want a slider, some a list. Some want the icons on the left, some want it on the right and so on and on. ;)

Where is the WYSIWYG editor? You need a serious & modern template builder for that otherwise merchants will fail anway...

@douclas I am confused. Are you a developper? Or you mean just like a brainstorming? Other example: https://www.prozis.com/ww/en/prozis/prozis-corehr-smartband-with-heart-rate-monitor (check the product description)

Right now I see many things on this site, which can't be done with tb easily. Even something simple like the about page: https://www.prozis.com/ww/en/about-us Very hard to make it like that in tb. That's why I always say, that this plattform needs to go on. :)

I just look a bit at it. It's indeed a very good example of ecommerce. Love it! But it's not a tb store, is it?

Ich habe es jetzt gerade noch einmal mit multilang probiert, hat auch funktioniert. Wie sieht denn der Kunde im Backoffice aus?

But I am bit confused. you try to give points, but actually you are working with coins aren't you?

Have you debug mode on? doesn't it say anything?

Hm strange. Have you filled in all languages title and description?

I have done a little change. Could you test, if this fixes your issue? I can't test it myself easily, since I am not using this feature: https://github.com/eschiendorfer/genzo_krona/commit/df5049a3958881356fc5f9ca67cc172f2404c5e5