wakabayashi

I don't think this fix will change anything on payment amount...

IMO you need to integreate APIs/Hooks for payment modules. If you edit an order, you can not just assume, that the paid value has changed. In practice there are multiple cases. Sometimes there happens a refund, sometimes the order hasn't been paid at all at this point.

I am quite sure that, it is not a bug, but bad design. The ps was designed, that every order is paid during checkout. As well they are kind of expecting, that an order doesn't get changed. I know, that my answer isn't really helpful. I am voting for years, for a better way of handling this. But it's very hard to achieve. The concequences are hard to forseen. For the payment case, I believe that a payment module should call a hook, so the amount get's corrected...

You have very nice products. Love them! I just quickly checked the categories and products a bit. I believe, customized text should be improved. I would add that above addToCart Button.

@justinrosander welcome to our forum 🙂 Try to deactivate Demo-Modus on the top right.

I am not from the official team, but my answer still would be: YES! We all know: if tb would now just give a shit on 1.6 support. It would die immediately. In my opionion it's much more likely that 1.6 won't work anymore, since smarty, php, or any browser forces for updates. When such a technical change will hapen, nobody can tell. But it will happen. And with some modifications the old ps modules can probably be even used after this kind of revolution. So really don't worry too much. You have anyway no alternative 😆

@Theo You are argumenting as ps 1.6 would be an alive project. It will die sooner or later. Devs won't upgrade their 1.6 modules at some point (I believe some devs already left or focus only on 1.7). But as an example: in our country there soon will be a new way of invoicing. It will happen with QR Code. If I am lucky, there will still be a ps dev that says: "oh ok, 1.6 will still bring enough revenue. I will publish a new module." but what, if not? We are living in digital age. Time is moving fast. What if browser come up with new rules? What if a new php version isn't compatible with 1.6 modules? TB is now great, but if there is no plan to move forward, the project will die for sure. In Short: The 1.6 modules support gives tb a basement right now, but it won't save tb for the future. AGAIN: Nobody said, that this basement should be errupted now for no reason.

@Theo You are too nervous. Nobody stated that 1.6 compability will be given up soon. And as you stated yourself, the modules are working right now. The point @toplakd wanted to make (and I completly agree on it). This project has to move forward. This is done with so much attention, that almost every 1.6 ps module is working out of the box. But seriously this project is now 3 years old. The most of the 1.6 ps merchant's now won't switch over. They have had enough time. How long do you wanna wait for them? Btw: I use the advanced search 4 module too. It's feature rich, but actually crap. It's slows down your shop so much... Look at @toplakd shop. He has a very slim setup without many external modules. He doesn't even need the smarty cache to have a super fast website. When it comes to feature values. I propose since years, that multiple values should be supported from the core. External module don't help here much as the multiple values won't be used by other external modules then...

Beacause you don't have smarty cache enabled, probably.

@rubben1985 the folder I posted myself cache/smarty/cache

@datakick I have checked my issue again. I found out, that the hook, which is called in a tpl file is cached strangely. My structure is like this: blocknewproducts displays blocknewproducts_home.tpl blocknewproducts_home.tpl includes product-list-slider.tpl product-list-slider calls {hook h='productImageHover' id_product=$product.id_product rewrite=$product.link_rewrite name={$product.name}} blockspecials-home|20200303|1|3|1|1|1|19 is the path to cache file followed by some more folders. But the cache of the hook is just not multistore ready. Strangely it only happens for the first time the hook is called. For some reason there are also cached files (yellow folders) of the called hook. But the imagehover module doesn't make this cache itself... @rubben1985 how does your cached folder structure look like?

Probably because this versions are outdated.

Works normal here. Never used this tool before, is it worth it?

I have a multistore cache issue too. But this is since two years or so. Really not sure, if it's related to this. My issue is really strange and I invested multiple hours and couldn't fix it myself some months ago. It happens on the blocknewproducts/blockspecials module. With the module itself, everything is fine. But I call a hook in the tpl and this cache, is somehow not multistore ready. Checkout https://www.spielezar.ch/ and hover motocycles comiot. You will see that the hover image is wrong. Strangely it happens always only on the first hover. On my second shop: https://www.puzzlepoint.ch/ it's correct. Update: After testing the display error disappeard, since the cache, was somehow refreshed. But this doesn't mean the issue is solved. I try to look a bit into the issue. But I can already remember, that it's a smarty cache issue.

A redesign won't happen (soon). If there is a clear bug, you can report it on github and it will be fixed sooner or later. If you are lucky, you will find a wms system that can connect to prestashop/thirtybees and works well for you. I know, that it is a bit sad, that I (soon) have powerful system (with product sales forecasting, chaotic storage, product scanners and much more) and it's not available for others. But I just can't share it: - Technically it changes a lot of stuff. An own bundle system was implemented as the core bundles don't know combinations. - It was coded for us. The needs differ from merchant to merchant. So some stuff would be completly obsolete, other things are missing, which we don't need. - I work on this project since two years (ofc not 100% of my time, but still). I believe, what I achieved it actually quite worth some money. I don't need an expensive WMS. I don't need a service like https://www.inventory-planner.com/ and so on... In short: Even it would be possible, I wouldn't share this (for free). Actually very important: Always define your needs. Maybe it's possible to propose you a module, which will work for you. Or maybe there doens't need to be too much core modification, to achieve it. So what is your need?

You are probably right. I don't remember all issues anymore. I filled a lot on github. But two years back, I was the only one who was really interested in this ASM stuff. I ended up in coding a lot custom (Like an ERP or WMS system) stuff for us.I forgot about this price stats, bu I bet all my money, that this was never implemented cleanly as there are much more basic stuff, that is even working. My best advise: Prevent combinations whenever you can!

To open a bug report on github is very easy: https://github.com/thirtybees/thirtybees/issues - Just click on New Issue and use a self speaking title. It will also propose you already existing issues, that could be the same or related. Check them out, before you open a new one. - Describe your problem in a way, that somebody with a clean thirtybees installation could reproduce it. - If there is an error message, copy it. Also check, if there is something in the browser console. - Screenshots or short videos can help. - Say which tb version you use. It can also be helpful to know the php version.

I didn't wanna say, that it doesn't get fixed, if only one person reports it. But the past has showed, if only one person reports a bug, it is often caused by server configuration, external module or external theme. Now with your report, this case became much more unlikely. To make clear: I didn't want to offend you or something. We are always thankful for clear bug reports 🙂 Right now, I believe only datakick is fixing bugs.

Please use search, before you open a new thread: It's not only good for the forum. Also for you. If multiple persons report the same bug, it is quite clear, that it's a real issue 🙂

One way is to hide. The other way is, to remove it from tpl. We had issues with the first solution, as there were some autofill or old customer data problems. Users saw something like "Your Birthday is not valid". But ofc they didn't even see any birthday select. Thats why we removed it completly from the tpl.

Well It clearly says, that you use an override. So the error will come from there... Either you have added an override or (more likely) an external module.

Or what are you talking about?

@movieseals are you using this module for speed optimization? I can only say this: thirtybees is quite fast without any external modules. You also don't need this "Full Page Cache" as @zen correctly pointed out. If your website is slow: check your hoster or the external modules. When I have performance issues in 95% the reason is due to a shitty external module.

Thirtybees cookies are first-party cookies. So no need to worry, IMO.

I can't answer your question. But in general I would just use the working solution you have got. I believe you won't get any big problem, if you use the reCaptcha module in the eu.