wakabayashi

@Chiel what is your concrete question? I general my opinion is: ASM (and bundle management) should be redone from scratch. But you should try it out yourself. For some needs it works, for some not. If you find bugs, please report them.

@datakick said in Full Page Cache - please do not use this feature: @wakabayashi said in Full Page Cache - please do not use this feature: @datakick I am still very confused about red and green? Did you change this mechanics? I am on 1.0.3 and there green means: always load the hook without cache! In 1.0.7, as a result of changing behavior from opt-out to opt in, the colors are inverted. Red color now means slow (non-cached) hook, green means fast / cached hook. I believe this is what everyone would expect, anyway. You are right, in previous versions the colors were inverted, the green meant slow and red was fast. Weird Thanks a lot for the clarification @datakick! I agree, that the new system is much better, as the old one confused 90% of the users!

Normally it works for us, if I redo the order.

@datakick I am still very confused about red and green? Did you change this mechanics? I am on 1.0.3 and there green means: always load the hook without cache!

So this is kind of a marketplace? I am not aware, that there would exist a complete database map.

I am still on tb 1.0.3 and blockmyaccount is hooked to displayHeader.

How many products do you have? Cause if you haven't too much, I would just add them to the backoffice... You must understand that you can't just copy one table over and it's done. Opencart has different columns than tb.

Ah maybe I got it wrong... You just wanna migrate your opencart data to thirtybees? Then surely go for cart2cart or add them manually in the backoffice.

Very hard to tell. It also depends if the products have attributes/combinations. I believe you also need to fill tbproductshop. If you are working with stock quantities, you probably need to look for tbstockavailable.

I surely would delete cache/class_index.php trough FTP. Just to make sure it was newly generated.

Ok I have to admit, that I almost never add hooks like that. But can't you play a bit around? Maybe comment the other hooks out and see if they still appear. I am confused, since you wrote, you use ps and tb module. Maybe a mess happened somewhere. Also check if the correct files are on the FTP server. Sometimes upload doesn't work :)

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