Leaderboard

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.

Database, PREFIX_employee table, campaign_disabled field. Set the date 100 years in the future.

Oh dear, good grief! There's no need to send an email to the shop using an email program. The regulation specifies a button that may link to a form. The form can be pre-filled or not; there are no further regulations regarding this. And yes, when the "confirm cancellation" button is clicked, the shop receives a notification in the background. The regulation, effective from June, simply aims to prevent customers from having to use an email program, a letter, a fax, or even a carrier pigeon. That's the basic idea. The customer simply fills out a form or checks a box, and then submits the declaration that they wish to cancel the order. Why is so much more being read into the regulation than it actually stipulates? Thanks @vir for your post before.

Thank you for doing this ... Enjoy your coffee ... Cheers

Any news on an updated Mollie module?

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

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

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.

Then the proper message you should communicate is: We need X amount of paying members to do Y. We have Z members. Or: We need X monthly income to do Y. We have Z monthly income. Don't just say: Become a member. Give people data, a funding goal, etc. You see that the calls to donate haven't been working amazingly. Try something new. And yes, it's hard work.