All Activity

hi. the mandatory withdrawal button is a new legal requirement in the European Union (Directive 2023/2673), effective from 19 June 2026, designed to make it as easy for consumers to withdraw from online contracts as it is to conclude them. More details here: https://psitsolution.com/tools/en/info/eu-directive-eu-20232673-of-2023-mandatory-withdrawal-button-from-june-2026 It might be useful: the thirtybees module to implement and comply with the new legislation can be found here: https://psitsolution.com/tools/en/thirtybees-ps-mandatory-withdrawal-button-module

I have been using the free versions of Google Gemini and Microsoft Co-Pilot and am somewhat impressed. Since I'm retired and just do some stuff as a hobby I don't do enough development work to justify paying for a plan. I prefer Gemini since it can "see" the tabs I'm working in. Sometimes it gets stuck in a circular loop that makes the same mistakes when I am trying to debug an issue or it breaks something the was working when it makes a change, and will make the same mistake more than once. In general it is much more efficient than I am. I used Co-pilot to help Gemini solve one of my circular loop debug efforts and it corrected Gemini on the first try. I feed that output back to Gemini and moved on further in my regression testing. I copy and paste between the AI and my source as it has no direct connection to the source. I gave Gemini a set of ground rules and frequently tell it to go back and redo complying with the rules, otherwise it starts changing stuff I did not want touched. Here are some rules I gave it to adhere to when generating or updating my code: The mandatory ground rules found in the testing document are as follows: 1. Preservation of Comments: Preserve any comments or annotations in the existing code. 2. No Unauthorized Optimization: Do not optimize or change any existing code. Suggestions can be made for acceptance or rejection. 3. Patch Formatting: When providing a patch, specify the line before and after the patch for easy location. Use /** START xyz Change **/ as the first line and /** END xyz Change **/ as the last line for inserted code. These may be removed during final cleanup. 4. Incremental Updates: Perform updates one function at a time and ask for permission to proceed to the next item to allow for testing. 5. Source Code Requests: Request the source for whatever is being updated if it was not already pasted. Use that source for the update unless instructed otherwise. 6. Debug Output Encapsulation: All debug output support, which may be done in a production environment, must be encapsulated using the cm_is_super_admin() function to isolate the display. An example provided is: PHP /** START DEBUG ENCAPSULATION **/ if (cm_is_super_admin()) { /*** DEBUG PLACEHOLDER BELOW ***/ echo "<br>". __LINE__ . " data:<pre>" . print_r(array_keys($data), true) . "</pre>"; //DEBUG /*** DEBUG PLACEHOLDER ABOVE ***/ } /** END DEBUG ENCAPSULATION **/

For those who don't know yet, the mandatory withdrawal button is a new legal requirement in the European Union (Directive 2023/2673), effective from 19 June 2026, designed to make it as easy for consumers to withdraw from online contracts as it is to conclude them. More details here: https://psitsolution.com/tools/en/info/eu-directive-eu-20232673-of-2023-mandatory-withdrawal-button-from-june-2026 It might be useful: the thirtybees module to implement and comply with the new legislation can be found here: https://psitsolution.com/tools/en/thirtybees-ps-mandatory-withdrawal-button-module

2.10.2 - 03/16/2026 Fixed combinations never being exported even when the option was enabled Fixed meta titles/descriptions never being used in export even when the option was enabled Fixed out-of-stock products never being excluded even when the option was enabled Fixed purchase price (cost_of_goods_sold) fallback for combinations without wholesale price Fixed images being progressively lost for combinations without specific images Fixed shipping cost calculation receiving malformed price data Fixed export language silently falling back to wrong language for unknown countries Fixed AJAX date refresh crashing when no export file exists for a country Fixed PHP 5.6 compatibility (removed public const and type hints) Fixed feed URL generation on Windows servers Improved security on debug controller (strict comparison) Removed obsolete debug controller Fixed wrong flag displayed by default in categories tab 2.10.1 - 01/27/2026 Fixed a bug in stock export Fixed a bug with selecting custom product IDs Fixed a bug when exporting Cron to other modules

2.10.2 - 16/03/2026 Les combinaisons fixes ne sont jamais exportées, même lorsque l'option est activée Correction d'un problème où les méta-titres et méta-descriptions n'étaient jamais utilisés lors de l'exportation, même lorsque l'option était activée Correction d'un problème : les produits en rupture de stock n'étaient jamais exclus, même lorsque l'option était activée Solution de repli avec prix d'achat fixe (coût des marchandises vendues) pour les combinaisons sans prix de gros Correction d'un problème entraînant la perte progressive d'images pour les combinaisons ne comportant pas d'images spécifiques Correction du calcul des frais de port en cas de réception de données de prix incorrectes Correction d'un problème où la langue d'exportation basculait automatiquement vers une langue incorrecte pour les pays inconnus Correction d'un plantage lors de l'actualisation de la date via AJAX lorsqu'aucun fichier d'exportation n'existe pour un pays Correction de la compatibilité avec PHP 5.6 (suppression de « public const » et des indications de type) Correction de la génération d'URL de flux sur les serveurs Windows Sécurité renforcée sur le contrôleur de débogage (comparaison stricte) Suppression du contrôleur de débogage obsolète Correction d'un drapeau incorrect affiché par défaut dans l'onglet « Catégories » 2.10.1 - 27/01/2026 Correction d'un bug dans l'exportation des stocks Correction d'un bug lié à la sélection d'identifiants de produit personnalisés Correction d'un bug lors de l'exportation de Cron vers d'autres modules

3.8.2 - 03/16/2026 Fixed a bug where the modal window would not open when clicking the button after a product variation change Improved back-office information page layout Fixed XSS vulnerabilities in the contact form processing Added product link validation in the form submission Fixed product cover image error handling when image is unavailable Added missing product variation field in the PrestaShop 1.6 form template Code quality improvements and coding standards compliance

Hello, Petter, we can help with Thirty Bees migrations. Our team has been working with PrestaShop and Thirty Bees for more than 10 years and we regularly handle migrations from different platforms and older PS versions. If you are interested, send us some details about your current shop (number of products, modules, customizations, etc.) and we can take a look. Email: [email protected]

Hi! Are there any experienced Thiry bees developers here who can undertake paid work with upgrading to Thirybees from Prestasop 1.6.24?

A connector to a newsletter service, a modified connector to LexOffice to send Amazon invoices to LexOffice, and a connector to the ShopVote API. But these are already for PS 8.2.

Does anyone know of a module that will allow you to enter multiple tracking numbers for a single order - TB1.4 Thanks in Advance!

Yes, this is a little bit annoying.

I miss possibility that if superior combination limiter is set then in lower impossible options are inactive. At the moment You can make all combinations and system gives to seller only message "This combination is not allowed" (or something similar).

I our local PS FB group, we had a lady merchant who was selling custom wedding lapel pins and other stuff. Her combinations per product were around 30k I think (5-6 dropdowns with many choices per dropdown). Of course, the system would fold... 😄

I see that someone else has also struggling with combinations. I haven't found anything better. Just need to think what You put in combination choice. I'm using also CSV import, without this is very very hard to manage combinations.

Currently, there is nothing better in thirty bees. Soon there will be packs with combinations feature. You will be able to create packs where customers will be able to select colors, etc. But you hit another snag - sizing will have to be arranged manually with the merchant as currently there is no option to select 5xS, 5xM, 5xL in a 15x pack. How many colors, sizes do you have? I have products with 11 colors and 10 sizes. If you combine personalization in the attributes, you're doing it wrong.

Well, think of a teamset for soccer, here we need sizes, colors and a lot more. When I create all this and click on combinations the system create to many combinations - So the system makes an error. That's the reason I think of there is a better way to do this?

Could you describe your process/idea?

@Alex Hansen It should be noted that all integrations and modules operate on standard attribute combinations. If you use a non-standard solution, it will not be compatible with anything.

No, it's going to be too complex 😞

Can't standard attribute combinations be used? The solution devised by Prestashop and adopted by Thirtybees is completely unsuitable for a large number of combinations. However, a few or a dozen attribute combinations can be handled.

If not just approach @datakick

Hi I'm looking for a solution to make several product combinations. Is there a good solution for this.

Yes, something like that was my intention. Maybe the thirtybees Team is looking for making some $ and sell this as a paid premium module.

It is pretty similar and all ways in programming need to be checked. The way Information is handled is different. People see a video and proclaim their opinion, often based on false information.

For sure, I'm not the first to come up with this idea, and precisely because of what nickz said (code quality) I will never release any of those as a paid module. Saying that, if anybody wants to further develop/maintain some of those modules or a later version is worthy of becoming a thirty bees free community module, I'm more than happy to assist.