DRMasterChief

Some kind of OT, but which pricing model do you use @vincentdenkspel? I have a look for some php work on https://openlaboratory.ai/models/CodeLlama-70B but the Claude Sonnet with Coding looks also interesting. Maybe we should split this here for future AI things?

We shouldn't mix things up too much here. And I do think that one more problem can create one more problem than the other. 🙂 The right to be forgotten, data deletion, etc., must be guaranteed, but this can also happen through a standard request and doesn't have to be an automated process (perhaps it's different in other countries). Most retailers will probably use an ERP system or CRM in addition to their online shop system, so a process within the online shop itself isn't very helpful, because the data also needs to be deleted from other systems. I would find it a shame if the discussion and search for a solution ended here. That's usually how it feels in forums when someone brings up a different idea. Let's work on solutions for the cancellation button, and if necessary, everyone can review the minimum legal requirements again.

I actually came across a case where something very similar was being complained about. It's not about a cancellation for goods, but rather the long-standing law regarding cancellations for subscriptions or financial services, etc. It concerns an offer from HP: (please use the translation for you language) https://www.bundesjustizamt.de/DE/Themen/Verbraucherrechte/VerbandsklageregisterMusterfeststellungsklagenregister/Verbandsklagenregister/Unterlassungsklagen/Klagen/2025/282/UKlag_282_2025_node.html

Canceling an order is not the same as returning an order—they are two completely different processes. >> I understand the regulation to mean that cancellation must be possible via a button, regardless of whether the order is partially or completely canceled. As already mentioned, the return process (if goods actually need to be returned) is then handled separately and manually or through some other automated method. This doesn't affect the required cancellation button; that's a separate issue. As you wrote, in such cases, the customer has to follow the standard return process, but that's precisely what they initiate with the cancellation button (but only the first step). Whether the retailer then (automatically) sends a return label, etc., is independent of this and must be considered separately (or it's a much larger, more complex solution with associated costs, as I've already mentioned). A customer who has no information about their order is not a customer. >> I understand that, but that's not the point the regulation stipulates. Thank you so much for your contributions. Let's continue to think about this and find solutions. I'd like to add something regarding guest tracking, specifically the issue of the unsubscribe button not being easily and clearly visible to everyone: I think this alone will cause problems or legal warnings. We would then have to explain to "the world out there" that the button exists, but is only accessible with some difficulty. That's precisely what the law doesn't want... How exactly this should be resolved isn't entirely clear at the moment. That's precisely why I had the idea to make the button clearly visible and always accessible at the beginning of the regulation. If, after some time, there are court rulings and experience with them, it can potentially be adjusted so that it can be moved to the customer menu.

I don't understand why everyone in the PrestaShop forum seems to think this is so terrible.... bla bla. I would take massive legal action against the provider, meaning multiple official reports to the data protection authorities in every country where a forum member resides. That's the intended course of action, that's all there is to it. It should be noted that payment data is also affected. There's no room for "oh, what a shame, blah blah," but rather, hard facts must follow.

There are certainly various possibilities, but the law provides clear rules. Of course, this also applies to guest orders. How do we handle it if not all items are returned? Is this sufficient in this form, or does it comply with the law? The button must also be accessible to customers who no longer have a confirmation email, who can't log in, etc. Thus, they also can't access the guest tracking information. And I don't think a cloned contact form requires too much information. As already mentioned, name and order number are actually sufficient. @Yabber What solution do you actually use (shown in the picture)?

Hello, thank you for your input. I have read several papers from lawyers and from the Chamber of Commerce. My concrete ideas are: we need to have a withdrawal button next to each order for the specified withdrawal period (by law or if extended by our policies) >> No, I don't want to make it that complicated, and there's no legal obligation to link it to the cancellation period. It's mandatory that the customer must be able to easily access the cancellation button anytime, anywhere (just like the legal notice). And it's important that they don't have to be logged in! It must be accessible to the customer even without logging in (e.g. for guest customers and if you have forgotten your password, it must be hold super simple for the customers). Of course, a customer could then press the button even after the cancellation period has expired, but the right of cancellation is quite clear about that, and once the time has passed, the cancellation is no longer effective (or, as a retailer, you can handle it however you like). However, I definitely want to avoid a very complicated implementation in the back office and don't want to automate any checks using back office data. The cancellation button must always be visible on the front end anyway. we should lead the customer to another page where they can confirm the request of withdrawal >> Yes, but easily accessible. I would therefore like to simply place the cancellation button in the footer, where information about shipping costs, legal notice, etc., is also found. The refund process does not need to be initiated simultaneously, nor does it need to be started digitally. This is generally covered by the right of withdrawal or the retailer's terms and conditions. we should send them email with the details of the withdrawal request >> Yes, a very simple confirmation that the cancellation has been received is sufficient. I believe that the retailer will then check it manually anyway. If you are a large retailer who has to process many returns a day, you will have a different, expensive solution programmed including payment management etc. We should have this solution simple and easy for smaller retailers. My specific idea is therefore to clone the contact form including the controller (with a new name). It already includes everything necessary: The subject selection function (customer service, etc.) should even be deleted. The heading should be renamed "Cancellation." The submit button must also be renamed, and a new email template should be created, which will then be automatically sent (by the cloned Controller) to the customer and the retailer. It is of course necessary to have a field for the customer's name and email address, as well as the order number if applicable. You might also want to include a field for the postal code to ensure consistency with the customer data and prevent misuse (however, this presents a legal hurdle). On this cancellation form, we can include a fixed text so that the customer automatically declares their cancellation. It may be helpful to add a free text field so that the customer can indicate if they are only cancelling part of the purchase. Just like with the contact form, you should probably include Turnstile (or another Captcha) to prevent the form from being misused by bots.

Hi everyone, Has no one really looked into this yet? It's coming into effect across the EU in June. I can't believe no one has started working on a solution yet. I think a paid module for this is overkill, especially since you can easily put together your own solution. Or perhaps offering a small paid module / code solution would be a good option for ThirtyBees, considering future financing, etc. @Acer Here's my post in the German forum, where I'm already working on a solution: Widerrufsbutton - Deutsches Forum - Generelle Fragen - thirty bees forum

@30knees danke für dein "like", kannst du daran mitarbeiten oder etwas beitragen? Wir sollten hier in der Community eine einfache Lösung erarbeiten, das wäre doch toll. (not sure if you will read this in English 🙂 )

Okay, we're getting quite off-topic here. But that's okay, right? 🙂 I wrote a long time ago that charging a low monthly fee can be a good approach. It absolutely mustn't scare off potential customers. It's (nowadays) very important to reach small retailers/shops that don't have a large budget. This is exactly where Thirtybees would be a great solution, and $4-5 per month for the shop as pure software would be fantastic. Payable every six months in advance. If that's too complicated to implement, offer a free 30-day trial or something similar. Then the license would need to be activated. It's important that no money-grubbing third-party provider does this (no Envato, please). And of course, it has to work flawlessly. I'd be happy to receive a license via email and have me insert it into a config file and upload it—no problem. I'm fine with that. In addition, there could be paid premium modules for ThirtyBees (as has already begun). That's fair, because nowadays it's also important to only pay for what you need. One more important point: Some information about ThirtyBees is extremely outdated. The demo, changelog, version roadmap, etc. It's also not entirely clear how and for what purpose paid support is provided; this urgently needs to be revised.

Good for customers? Time will tell. In any case, a lot would have to change. The current model is no longer suitable for e-commerce today (from the retailers' perspective).

@netamismb you can find a lot of ideas for an update here in this section: Updating thirty bees - thirty bees forum

Hi, many thirty-bees/PrestaShop themes provide the variable `$cart` in the shopping cart template. Then, in the template, you can simply add: smarty {* show Cart ID *} div class="cart-id"> Cart ID: {$cart->id} </div> If it's not already available, you'll need to pass the Cart ID to Smarty via a controller. The correct controller for the shopping cart is `CartController` (controllers/front/CartController.php) (or for one-page checkout: `OrderController`, I think, you'll need to check that). If you have to retrieve it via a controller, I would create an override for it so that it persists after an update.

thank you, appreciate this! (i will save this time 🤙)

Great! and can i implement this (manually) also in 1.6 ? (i get this error with php8.1 and want to fix it for my update in live-shop)

Thanks for the hint; I wouldn't have expected to find something like that there. I'm sure I've seen it before, but after a while, you don't think to look for it under 'Languages'. I've already changed the 404.gif image (or the equivalent for my theme) to a blank 1kB image. That works fine, and it now displays as I want. However, I still don't quite understand the reason. The image settings, etc., are correct and identical to my shop version 1.5.1.

I have the same error with the update to php 8.1, is there any solution? I am not sure to code something for my own here, regarding it seems to be deep in the Core and it is about the shopping cart - i dont want to crash this 🤓 You can see that there is the Id 26683, but this does not exist. It seems to be an updated address and is now (customer) Id 26684. Warning Message: Attempt to update unsaved object Location: classes/ObjectModel.php line 752 Stacktrace #0 builtin #1 classes/ObjectModel.php(752): trigger_error("Attempt to update unsaved object", 512) #2 classes/Cart.php(2809): ObjectModelCore->update(false) #3 classes/Cart.php(2769): CartCore->update() #4 controllers/front/AddressController.php(307): CartCore->updateAddressId(26683, "26684") #5 controllers/front/AddressController.php(129): AddressControllerCore->processSubmitAddress() #6 classes/controller/Controller.php(198): AddressControllerCore->postProcess() #7 classes/controller/FrontController.php(264): ControllerCore->run() #8 classes/Dispatcher.php(858): FrontControllerCore->run() #9 index.php(33): DispatcherCore->dispatch()

I'm having problems with product images, not category images. When I look at the category overview, I see the placeholder (the product correctly has no image). When I then look at the product details, I don't see a placeholder, just nothing (white, since it has no image).

ok, would it be a good idea then to do this automatically, when there is no pic given? e.g. by PHP (m I correct in this?): <?php $img = imagecreatetruecolor(1, 1); imagesavealpha($img, true); $transparent = imagecolorallocatealpha($img, 255, 255, 255, 127); imagefill($img, 0, 0, $transparent); header('Content-Type: image/png'); imagepng($img); imagedestroy($img); ?>

Yes, everything is done as described, set SEO/URL, regenerate all pictures and so on... Changes does not have any effect. Test shop: # categoriesthumb images RewriteCond %{HTTP_HOST} ^test.domain.xyz$ RewriteRule ^categoriesthumb/([0-9]+)(\-[_a-zA-Z0-9\s-]*)?/.+?([2-4]x)?\.(avif|gif|jpeg|jpg|png|webp)$ %{ENV:REWRITEBASE}img/c/thumb/$1$2$3.$4 [L] Live shop: (i think this is the part for categoriesthumb images, i do not have a listing with # in there) RewriteCond %{HTTP_HOST} ^livedomain.xyz$ RewriteRule ^c/([0-9]+)(\-[\.*_a-zA-Z0-9\s-]*)(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/c/$1$2$3$4.jpg [L] RewriteRule ^c/([a-zA-Z\s_-]+)(-[0-9]+)?/.+?([2-4]x)?\.jpg$ %{ENV:REWRITEBASE}img/c/$1$2$3.jpg [L] and i dont have any other overrides for pictures (caused in the theme). There is the folder /thumb/ included in the test-shop rule, but why?

Was any solution found for this? Or what triggered it? I'm experiencing a situation where, after updating to version 1.6, the thumbnails in the category previews are populated with the camera icon when there's no actual image. Previously, nothing was displayed there at all, just a blank white space. I have the .htaccess files from versions 1.5.1 and 1.6 for comparison, but of course, I'm stuck.

Thanks for the info. I knew about the other topic but couldn't find it right away (the one from the link). However, my experience is different; the camera icon is displayed in the category overview, but it's white in the article itself.

Hi Yabber, not sure about thirtybees 1.7.0 (can anyone tell the details for changes from 1.6 to 1.7 ?). My theme is well-programmed and stable, but at some point it will probably come to an end... but yes, i will try in the next days. Most important is to have the live-shop at php8.1 Now on version 1.6, it shows me the empty images (placeholder camera) for articles without a picture... hmm, so simple, but how do I change that?

Yes, the direct jump to 8.1 isn't documented in the manual, but it shouldn't really matter whether it's 8.0 or 8.1... I'm very careful to use only absolutely necessary modules. This saves a lot of time and effort when such a change is needed. But i have some manually changes to some files (mostly theme-related for a good look). The modules and the theme I'm using don't seem to have any problems with PHP 8.1. I'll be monitoring the collect logs for a while now. All tests are still being conducted in the test system. If nothing unusual comes up, I'll make the same changes to the live shop.

Hmm, okay. I see that `nd_pdo_mysql` isn't loaded under PHP 8.0, but it is under PHP 8.1 (and I can't change that while testing). Just so you know, I'm currently only changing the PHP version for a single directory (for testing purposes, there's a test shop in a subdirectory with a subdomain). I do this by .htaccess . Maybe this can cause the problem? So I have to switch from PHP 7.4 to 8.1 (which is rather unusual, I think).