musicmaster

The only type of image that could cause such an effect would be a very large image. But I believe that software should be capable of handling such cases. If I remember well Prestashop used to downsize images to a certain size during upload. Michael took that out as it had a negative effect on image quality. Maybe there should be some other mechanism to handle this?

So if I understand you well Havouza should just have to run Image regeneration a few times more and all his images will be ready. In that case the page could use some improvement in self documentation.

You can use Prestools to regenerate the images. It allows you to state which images to regenerate - which image numbers and which formats. It amazes me that I cannot find an option in TB to generate only missing images - as Prestashop always had and still has. Am I missing something?

Buying support for templates is rather common. They are complex beasts so it is quite common to find something in some corner not working ok. In fact Thirty Bees saves you money as it has some more functions so you will have to buy less modules. The more serious problem with the templates is that the average template provider doesn't support Thirty Bees. So in order to receive support you will often need to maintain a parallel copy of Prestashop to certify that the problem you found also happens in Prestashop. Having a list of what to expect would do a lot to convince more template makers to support Thirty Bees.

I believe that one of the things that is holding people back from migrating from Prestashop to Thirty Bees is that although people often say that it is easy to adapt modules and templates there is never any clear description of what has been done. Saying it is easy is from my point of view not very helpful as not everybody is as competent with software and even very skilled people can overlook things and discover much later that they have a serious problem. That is why I would love to see concrete descriptions. What was really changed? Was it just some cosmetic adjustment that you would have made under Prestashop too? Is Thirty Bees providing different data to the template than Prestashop. Is there something else different in the mechanism? Or does it have some underlying style sheet that is different?

I have a product without an image. In the category view it looks like expected: the drawn camera. However, on the product page I get instead the Dutch flag. Does anyone have an idea where this could come from?

Can you share what kind of modifications are needed?

Which file produces the error?

Be careful upgrading Panda. Panda versions 14 and 15 are very different. They have different modules and there is even a hook on a different place. Their website says that you must run 15 with TB 1.1 but it is not clear to me why. 14 worked perfectly for me with 1.1 - with only a fix for the “Cannot use object of type carrier as array” problem caused by the Smarty upgrade. Also I didn't like their redesign of the checkout page in version 15. They have changed the page in a way that makes it easier to overlook the login link. And then existing customers try to create a new account. That results in an error message that they don't see as it is above the form outside the visible part of the page. So they conclude that the Save button doesn't work and your webshop is defect.

Did you investigate whether the combination Easy Checkout-Stripe works on Prestashop 1.6?

I use Stripe on the Prestools website, I regularly receive payments through it and I haven't received complaints. So maybe there is some instability in your shop outside TB and Stripe.

Can you explain that? I don't understand what you mean.

Paypal, Stripe and Mollie all work ok for me.

You might consider submitting an error report in Github. Anyway, to help you a little further: The file where this is handled is /controllers/front/ParentOrderController.php The code handling it start with: if (Tools::isSubmit('submitReorder') && $idOrder = (int) Tools::getValue('id_order')) In the (older) version where I checked this it was at line 87.

I ended up upgrading to 2.3.7 - that was recently released. This solved the problems.