Daresh

I'm quite happy with PS8. In my opinion, version 1.7 was something to be waited out — it had many sub-versions that differed significantly from one another. And I often had cases where clients came to me asking to fix a bug in a specific 1.7 version, and after analyzing it, it turned out that everything had already been resolved in version 8, some of it started in version 1.7.8. I hate everything lower than 1.7.8. I’m just starting to work with version 9, but it seems more like an evolution of version 8 rather than a major shift. I don’t want to come across as a PrestaShop evangelist among ThirtyBees users — I’m just sharing my personal experience. Thanks to the large number of hooks, the child theme mechanism, and the well-organized file structure in the template, working with it is simply enjoyable for me. I'm especially happy with hooks for stuff like: adding custom content to carriers adding custom terms and conditions adding custom tabs to products adding custom flags to products adding or removing columns in back office listings and so on...

I did something like this for one of my PS customers. But it's rather to be done with theme changes, not by a module. The key there was to replace the single quantity selector with a dropdown, allowing the customer to only select packs. This way the customer is not able to add 12 pieces and change to 13, it can only be done by increments of 12. [example]

From a developer’s perspective, I can say that working with PrestaShop since version 1.7.8 has been a very good experience. A large number of new hooks have been added, which allow me to create modules for my clients in a clean way — without overrides, and without modifying the template or the core engine. When developing a module for the general market, I try to provide support for version 1.6 and ThirtyBees as well, but it's not always possible to do so in a clean and maintainable way. On the other hand, the complexity of PrestaShop's code has increased significantly — as if it were being developed primarily for tech-savvy users rather than for merchants in the first place. I see many flaws in the project, and I’m not surprised it might be losing market share. Nevertheless, I’m still able to build a wide variety of stores on this platform and efficiently add new features to them as needed. Another important factor is support from couriers and payment gateways. Many of our local Polish companies develop their modules exclusively for PrestaShop, often only for version 1.7. That’s why clients who come to us tend to choose PrestaShop and ask us to build their stores using this software.

Thanks, in case of any other general suggestions, just post them here:

And thanks to your fantastic feedback, the module can now display GPSR information in a tab for Warehouse theme users without requiring any code modifications.

Sure! A lot depends on whether your current template is designed to organize content into tabs. Could you provide a link to your store, or even better, attach the `product.tpl` file from your template?

That can be achieved using the custom hook along with some simple TPL changes. I’ve already implemented such a solution for one of my PrestaShop 1.6 customers (example).

The demo is actually on PrestaShop 1.7, which has a separate hook for tabs. However, this is not the case for ThirtyBees, where the module is hooked by default to the displayFooterProduct hook. As a result, its appearance is more similar to what is shown in this demo: http://demo.greenmousestudio.com/tshirts/1-faded-short-sleeves-tshirt.html If that doesn't fit your needs, the module includes a custom hook that can be placed anywhere on the product page.

Hi Guys! Are you getting ready to the new EU Law regarding product safety. Here is a short summary about what it requires from store owners. When selling remotely via a website, the product listing must include: Manufacturer's details: the full name or registered name, registered trade name, or registered trademark of the manufacturer, as well as the postal and electronic address where they can be contacted; If the manufacturer does not have a residence or registered office in the EU/EEA: the full name or name, postal address, and electronic address of the responsible person (responsible entity); Information to identify the product, including its image, type, and other product identifiers; Any warnings or safety information. I already have a module that helps stores to comply with it, but in case you have any questions let me know, as I've been studying the subject a bit lately.

Good for you! But I think a new thread regarding the GPSR Directive may be a good idea. Many stores are still unprepared, and there is much to do in some cases.

Hi guys. If you are looking for this specific solution because of the GPSR directive, check out the GaPSeR module, that I recently developed, it also supports 30Bees :)

The error you mention is related to the same ThirtyBees bug that was discovered some time ago. The notice is a minor thing, it shows up because you don't have any previous prices gathered in the history yet.

Thanks for noticing my module. Yes I made it work on PrestaShop 1.6 so ThirtyBees is also supported. Actually the module helped to discover a ThirtyBees bug in a customer counting function. So in case of any questions I can explain the logic of the module or the new law, so it's clear for everyone. From what I know, PrestaShop team is currently not planning to introduce such a feature in the core, so I think the same is for ThirtyBees and we need to use modules. A function of this kind can be considered an extension of the base functionality. It does not require to override any core functionality so that's a good thing. Everything can be achieved here with hooks.

Did you solve this problem? Cause I'm having the same issue now after making a copy of the shop to another domain.

Right, very interesting, never had an issue like this before and thousands of shops use this module. Must be some kind of an unlucky coincidence...