wakabayashi

For me its not clear, what your question is / what you want to achieve. As far as I understand now, you want to use this bool on product.tpl. Is this correct? In general I would prefer to go with a module instead of changing core files. You would just need a table with (id_product, your_bool) and then load a your custom hook on product.tpl.

Yeah I just installed this version, which was there for tb. It works out quite good for us. So I didn't and don't want to change anything...

In my BO log I have similair warning: Warenkorb kann nicht geladen werden. Eine Bestellung mit diesem Warenkorb ist bereits vorhanden. Thats not good, but I don't think it's the reason for the problem.

Which Mollie version do you use? I use v.3.1.0!

Have you checked your cronJobs? Is it always exactly 25 days or does it differ? Does it happen always on the same hour or so?

Could be hard to get an answer for this. Not a lot of people us ASM. We do, but only with one warehouse. So I can't tell 100% but I never have seen any setting to set this off. Are you sure its new in TB? Then it could be a bug. But it would surprise me a bit, since ASM wasn't touched a lot...

I dont think it's Mollie. We are using this module and don't have any such issue.

I guess it's a module...

It could be a class issue. As far as I remember one can define a class, where the elasticsearch results are put in. Is this right? In general: Does the funcionality work out for you in elasticsearch? When I was looking at it, I had the feeling that the module wasn't finished.

Nice to have the new forum! I agree with @DRMasterChief that the contrast should be higher.

@hedgehog interesting finding. Ofc this can happen with other languages too...

@RabbitZzZ thx a lot for looking that deep into it. You were right, I was wrong! Sorry for that. @datakick thx a lot for the fix.

@Domas Sorry I don't have time now, to find a solution.

Not sure. In general this sounds a bit strange to me. You have multiple times the same reference? I have just googled. Maybe this works: // get a list of sort columns and their data to pass to array_multisort $sort = array(); foreach($products as $k=>$v) { $sort['reference'][$k] = $v['reference']; $sort['location'][$k] = $v['location']; } // sort by event_type desc and then title asc array_multisort($sort['reference'], SORT_DESC, $sort['location'], SORT_ASC,$products);

@Domas search in file AdminOrdersController.php for the function "getProducts($order)" And try to add this before the return: array_multisort( array_column($products, "reference"), SORT_ASC, $products ); If it works, I would suggest to make an override afterwards...

@piet thats probably not what he is lookin for. I believe he is talking about the BO. There you would need to change a controller, I guess. Maybe a tpl file could also work.

@gandalf @gonssal I haven't thought in detail about it, but I would probably go the same way.

Thx a lot! I will soon try it out :)

I don't think you need to change anything then. Or do you have any issues?

You still us ps? :S

@nickon said in GitUpdater preview: This is a feature I always whished for. Especially the downgrade part. I would like a checkbox so I would be able to uncheck a specific file I don't want to update. (all files checked by default) I don't know how database changes are handled though. This is something I always wanted for tb. To be stable and add features missing in 1.6 Keep up the great work. This is an intersting idea. But I guess, it can also make troubles. Imagine a new function is added to a file, which you don't update. Once this new function is called, your shop will throw an error. But of course I see your point. Especially for theme files, it could be helpful.

Maybe its related to this issue? https://github.com/thirtybees/thirtybees/issues/792

Damn thats bad... Maybe somebody else can confirm the issue?

I just don't think its a core issue, since we dont have it and @30knees also not. I would try two things: - disable overrides - do the same tests on a clean tb installation

@30knees just refresh the page and it looks normal again...