Leaderboard

It's a very interesting discussion here. I can understand both positions. It's really a chicken-egg game. But imo there is a huge game changer: AI. It has become way more simple and fast to write code. I am also not aware of the plans/roadmap of TB. But with the new AI tools, it's even possible for no coders to start modifying some stuff. Ofc it's always better, if you have some basic coding knowledge, otherwise you might mess things up. Even if you aren't brave enough to use AI yourself: I would guess, that prices for a custom module will come down a lot. @datakick what is your experience with AI these days? I would say it has speed up my developing work about 3-5 times. It's hard to tell, but it's for sure huge. The first time I have the feeling, that my todo-list may become shorter 🫣

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.

@vincentdenkspelI said not just ... not just not. :) I have also created some modules that work. It's amazing!

I also created other modules. I use a dutch version of 'trustpilot' (keurmerk.info) The module I created with ai is twofold: 1) after the status of on order becomes 'delivered' the module will send a 'message' to keurmerk.info. Keurmerk.info will than send a review request to the customer. I the module I can set how much days after status 'delivered' the info is send to keurmerk.info. 2) the second part of the module is that I will display the last 5 reviews on my site in a slider. The third module I have created is a bulk-list-picker. With this module I select orders and the module will create a list of the stock locations of the ordered product. I can select 'per order' or 'bulk' This module has a bug in it, but I hope to sort this out very soon. consolidated_picking_list_20260223_123059.pdf

I will. It is only on a test site. What I did: I uploaded the all Thirtybees 1.6.0 files in AI and had it analyse all the files. Based on the analysis I made AI create a 'Thirtybees module development guide' Whit this guide and my input I had ai create the module.

Hi, it is clearly stated: The withdrawal function shall be continuously available throughout the withdrawal period. Even if the button is displayed after the withdrawal period has expired, this is not a legal problem. There is no reliable technical way to calculate the withdrawal period in the shop. It depends on many factors, such as partial deliveries or whatever period the retailer voluntarily grants. The details of a partial cancellation of a larger order are not addressed in the EU directive. Thank you for that 😞 If a reliable way can be found to link the withdrawal period to the withdrawal period, that's fine. Please do so. However, if there is only one instance of an incorrect withdrawal period, it is not good for the retailer. The permanently displayed button naturally carries the risk that it will be used even after the withdrawal period has expired. However, this is not a problem; the withdrawal is then invalid. The retailer will have to check this in any case and inform the customer, etc. Then he has to inform the customer that the cancellation was received after the deadline, but this is no different from before, or if a customer still cancels by email. Just expose your guest tracking controller with a link in the footer for all guests, and that should suffice. >> Yes, that's true, but guests and logged-in customers can use it, except that the login process is (possibly) displayed afterward. This could be seen as an additional hurdle by logged-in customers > not good. I'm not sure if it's clear what I mean by that point? With all this in mind, I have to say that we actually don't have any cancellations/returns. Maybe I'm oversimplifying things? We simply have to implement it; only one customer will use it per year. But please let us discuss here further!

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 **/

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

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 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.

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.

I never worked with claude yet. It seems to be the best model. But right now I can use Codex 5.3 with no limits in phpstorm. I only pay the 20$ plan. Codex 5.3 is very strong as well. Maybe there are "political" reason to leave OpenAI but pricing and quality aren't an issue for me right now 😅

All the free AI offerings have a daily usage limit (or they even fake model versions.). Nothing is truly free if you're looking at cutting-edge models. However, http://poe.com/ offers some pretty good models for free.

OK, let stick to topic here and I will split it later tonight.\ EDIT - better late than ever... Let's discuss community modules and core additions made with AI here. Vibe coders - unite! My entries: antifraud module - sits in BO Orders and displays account info (number of orders, account age), device info (ip, location (based on external database), device, osint tools (sometimes it's usefull to check the customer email, phone in google if some order smells fishy - if they are present - most probably the order is OK). Also - 'soft ban' function - If I want to ban some customers and not fulfill their orders I can ban the account, the module tries to search for similar later registrations and notify me if it detects similar fingerprints. Also global account note - if I want to say something for later orders in this account it can be saved here. control center - offers a dragNdrop dashboard for merchants that want to see the high-level information - order by status, order profit by period, other KPIs, template export/import, etc My vision is when I 'become big' I will have this in my office on an LCD on the wall and only drink my Caipirinhas while looking at the numbers.... 🙂 dual currency display for our EUR adoption - similar to Croatia we have to display prices in both currencies for a period - in FO and emails, not a complete solution but works. Dynamic llms.txt per shop - set up a dynamic llms.txt file per shop in multistore IndexNow Integration - update search providers that support it. thirty bees File Integrity - most recent and still unfinished - goes through each file on the root and tracks edits, deletions, or new files. Using SQLlite it gives a quick note on what is changed on the server in all folders - useful to find malicious files on the server if they are placed, let's say in img where they are extremely hard to find manually Dynamic Robots - serves a dynamic robots.txt file in a multistore environment. And of course many attempts on core changes - visible in github.

I use abacus.ai. Although I like it, it although it has some disadvantage: you buy credits, but do not know how much credit a 'instruction' will cost.

Such a leak of customer data could result in huge fines for Prestashop. This is probably why the previous owners sold Prestashop so quickly.

Here is a description of the attack vector: https://www.prestashop.com/forums/topic/1105466-recent-prestashop-securtity-alert/?do=findComment&comment=3543558 Conclusion: Prestashop Addons Marketplace is a dangerous store where you should not provide any login details for your store. If you have provided your login details for your store on Prestashop Addons Marketplace, you should change them immediately.