musicmaster

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.

Thirty Bees already has more features than Prestashop. I don't see much urgency to add more at the moment. What I consider much more important is getting Prestashop users to switch over. I don't think the lack of features is stopping them. Rather it is a lack of templates and to a lesser extent modules. Sure, Thirty Bees offers support if you use templates and modules that aren't guaranteed by their makers to work with Thirty Bees. But that is a rather weak offer. It would be much better when they could point to a list of templates and modules that have been tested and found to work. In this light I would prefer to be reticent in adding new features. At this stage maintaining PS 1.6 compatibility is crucial and any addition is a risk factor for compatibility.

"Class not found" often happens when some class file is missing or damaged. So the first thing to check is the file /classes/shop/shop.php.

I don't get any problem updating the category title. Is Spanish your only language? Or is English also installed? Do you use multishop? Did you check the indexes of your _bees_blog_category_lang table?

My standard next step in this kind of situations is to disable pretty urls. That makes it much easier what file is looked for and what is there. But there are other potential trouble spots such as the spaces in the filenames and the "2x". Spaces are allowed when the filename is within quotes and that is sometimes a problem.

Thank you. I found a solution that works for me now.

"We are sorry, we only allow ticket purchases from internet addresses inside the united states." I can 't see your site.

I tried. After four answers that missed the point (my impression is that everything goes via Google Translate) I am about to give up.

Does anyone know how to program the mobile hamburger menu button under the Panda template?

I used to have such a thing with Prestashop 1.5. It probably was related to my template. Anyway, I got used to emptying the cache every time I changed the products on the front page. I haven't seen this problem with Thirty Bees.

Are you sure these are all your console errors/warnings? It takes only one unrelated javascript problem and then jQuery isn't loaded and you get all these follow-up errors. With javascript errors you should always look at the oldest first. All the rest can be follow-up errors caused by the first one.

When Jquery doesn't work it is usually because there was a javascript error before it was supposed to be loaded. So I am very curious how your javascript console looks.