wakabayashi

I am no JS Expert. I normally work with Jquery. But Vanilla JS is completly fine. Maybe a link to the site makes it easier to understand...

This custom code isn't the right place, to add new functionality. This is made for adding external js files (like Google Analytics or so). You can add the js code also in product.tpl. Just use something like: {literal}<script>Your code...</script>{/literal}

It happened to me multiple times, thats why I wrote it 😅

I would say you either look at a test db or an external module is doing a very bad override...

Actually it really should be updated as it's working. Have you sorted by id_order and checked, what the newest value is?

No problem. I understand. You need to adjust your theme. What theme are you using? Edit: you use community-theme-default. Have you tried to update your store to bleeding edge? Search the menu "core updater" and select "bleeding edge" and "1.1.x". Then upgrade. That way you get a lot of bugfixes.

Hello. You should use forum search, before asking such a question. This issue has been reported many times before:

@datakick Sorry. I was wrong. It's working here too...

Same here. Not sure if this was dropped or if it's just a bug.

What is this all about? :S

I can confirm that. I had never a single issue on anyting with php. Of course when you develop on js and use ajax you need to be a bit careful to delete the cache. But in general I am very happy with cloudflare.

From this screenshot I have no idea, where it comes from. Please show a bigger screenshot. So expierenced user will know, which module is relevant.

I will look again into this. But IMO this is not the case. It's true that 'updateShipping' is called always. This is because you can set a fixed amount of shipping. If you don't change this value and don't select recalculate, there is an update but with just the same values as you already had in DB. In my country this is a bit different. But I am aware that this can be an issue. That's why I created the form in the second commit. The form allows me to add an "invoice select". So every merchant can select the invoice, which should be updated. Right. I completly forgot about this shitty id_carrier change. But I believe, if I just add the "deleted/changed" carrier to the selector as well, this should be solved.

I understand ofc. We are already using it in our live store, but ofc other testers are needed. You mean in AdminLogs or something new? If it would be new, I believe we would better make a order history concept, that shows everything (like order status change, emails sent, customer messages, customer service cases) in a nice history tree or so. Have you briefly looked at the concept. How do you think about this: "Technically a new cart is created based on the order values. The cart is used then to recalculate the shipping cost."

Oh sorry, I can't help with this issue. I don't use this module.

@Briljander thanks a lot for your response! Is it this module? https://addons.prestashop.com/de/bestands-lieferantenmanagement/22049-advanced-order-processing.html Does this module just allow to set a fixed amount of shipping or does it also offer the "recalculate" feature?

https://www.payfast.co.za/integration/shopping-carts/prestashop download the older version for ps 1.6 and check, if it works.

I have invested another day. It's now possible to add fixed a fixed amount/weight. Also the hardcoded transit email can be fixed that way. Still my code is not totally finished: There needs to be validation check in the new updateShipping function. RMA seems to use "submitShippingNumber" as well. That's maybe not problematic. I don't use RMA at all. So no idea what this should do. After a click on edit, the form looks like this: Btw: For me this project is quite evident. My goal is clearly to push this into the core (after careful validations with merchants). If this doesn't workout, I won't supply anything in the future. Cause developping things for core, which doesn't get applied, is too costly: I invest a lot of time to be consistent with the core, if it's only for my own store, all is much faster and simpler. After a modification get declined, I have to rewrite again, since I need to use the code in an internal module instead of core. If this important (and much wanted) feature can't be implemented, I lose faith, that there will come any real progess on other topics (like asm, attributes on bundles/virtualProducts and so on...).

I don't have this file in my theme... But what about $order->payment

Was heisst nichts? 🙂 leere weisse Seite?

Not sure if I understand this right. Ist this about invoice.tpl?

great! 😍 enjoy it!

@RabbitZzZ, @toplakd, @datakick As I get mad almost once a week about the misssing "update shipping cost", I decided to tackle this myself. I couldn't wait any multiple years longer for this feature. In my opinion it's over due... As we pointed out above, there is no super clean solution to this problem, but I believe that my solution now is quite acceptable. At least it's much a cleaner way than the free PS module uses. Technically a new cart is created based on the order values. The cart is used then to recalculate the shipping cost. I practice you can select the shipping method in an order and click on "recalculate shipping cost". This is very useful in case you have edited the order before. The select also allows to change the shipping method at all. This way you can change, in case your customer wishes so or you can also select a shipping method, that is only visible in the BO. I haven't imlemented a amount input yet, but that would be possible too. I hope, that some expierenced user test my snipped (in a test store) and give a feedback. It's really hard to forseen every case. In my (quite simple) cases, the code seems to work properly. https://github.com/eschiendorfer/thirtybees/commit/4ccd64465ff1e4b956e1caba1feb411b6ee834a3

Who is they? Are you a dev? 😎 What about this: {"{$order_invoice->date_add}+{$customer->max_payment_days} days"|date_format:'%d.%m.%Y'}

Ok I understand your idea. Why don't you use: {$customer->max_payment_days} This should be available on invoice.tpl