musicmaster

Hello KoIS, As mentioned in the post Prestools is not a module but a script. So do not try to install it as a module but read the installation instructions.

This works nice when you take an existing system and upgrade the core in the hope of a bit more speed and stability. In that case you know that a problem was caused by this upgrade and you can roll it back. But the Core Updater system is a bit problematic when you are starting a new shop. If you go the TB download page you get version 1.1 from July last year. So you tend to upgrade it with Core Updater to the latest version. But now you have a problem: when you find a bug you don't know whether it is in TB, the template or some module. This could easily be solved by having more official versions that have extensively been tested for stability.

Having just encountered this thread I want to add my own two cents: - I appreciate all what Datakick has done for TB and hope that a solution can be found that keeps him involved. I wish Lesley a good recovery. - the core problem seems to me leadership. The fact that it is a company makes that only more complicated. It doesn't look like someone wants to buy it from Lesley at the moment. And it is unclear what is Lesley's plan B. - my idea for getting more users would be to get closer to Prestashop. Produce some free "got to have" PS 1.6 module (gdpr would have been an option) for PS 1.6 to build name recognition. There should be a module for migration from PS 1.7 (the database is almost the same as 1.6 so that shouldn't be particularly hard). There should also be modules to migrate back to Prestashop - or at least references to services like Cart2Cart. You cannot tell people that they will be locked in once they migrate to TB. And it shows confidence that they will stay. - the name Thirty Bees is a bit of a handicap. Most other webshops have a word like "shop", "commerce" or "cart" in their name that makes it much easier to recognize what they do. It doesn't help that we don't have a story behind the name that would help to remember it. Changing the name might be hard but one could consider changing the subtext and logo. - some people campaign for PS 1.7 compatibility. I don't see much potential there at the moment. If you look at the database the only real innovation of 1.7 is that you can have more than one value for one feature. For the rest it has a few extra database fields that quite likely are seldom used. There has been quite some discussion about multi-feature on the forum here - the code is there but some people expect problems with existing modules. - some people like the 1.7 development environment and specially the template. I think Prestashop is too much of a moving target at the moment for such an adoption to make sense. By the time the TB code would be ready PS might be at version 1.8/8.0 and have introduced some other major changes. - if you really want to add something distinctive to TB my choice would be headless ecommerce.

I uploaded a new Prestools version: 1.24n. It contains a new version of the image plugin too. The new version fixes a few issues with image edit: - you could not add an image to a product that didn't have any images. - when you marked a newly added image as cover it wasn't registered as such. As a consequence the product ended with no cover and you didn't see an image in the backoffice product list. - when you made the image field editable and the cover image was not the first one it displayed on the first position the cover image too. The editing is now more wysiwig as it makes that you to always have an active cover product. If you find any more problems please let me know.

New: the Image Edit plugin. It enables you to add and remove images in the product-edit page. You can also change their order and choose the cover image. It looks like this: The "X" button allows you to delete. Right below is the field for the cover selection. You can add images both by clicking the add button and selecting a file and by drag-and-drop. Changing the order goes by drag-and-drop too. As usual in Prestools all changes are only implemented after you submit. When you add an image it is uploaded to a temp directory below your Prestools directory. When you submit it is moved below your /img directory. Image (re)generation of formats like 123-small_default.jpg does not take place. You will need to that separately in Prestools or the Thirty Bees backoffice. As usual with new modules this one will be free to download for a few days on this location. People who have bought the full Prestools package can just download the latest version. It is included there. Note that this will only work on Prestools 1.24l and newer.

There are only two graphic libraries for PHP: the GD library that comes standard with PHP - and Imagick. Imagick delivers better quality and performance but can be a bit of a crime to install. Prestools doesn't use Michael Dekker's module but talks directly to Imagick.

Did you install all three: the ImageMagick program, the Imagic PHP plugin and the TB module? Most hosting providers have it pre-installed, but when you need to do it yourself it can be a bit complicated. I don't know which TB version you have. This is a rather recent addition.

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.

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?