DRMasterChief

i now have installed this fix and have an eye on this 🙂 thank you for fast response! btw. do you need more details about this error in my shop?

Hi, this can be done super simple in Database, do you have phpMyAdmin login? I hope so... just use the simple option...: Select your thirty bees database in phpMyAdmin Locate the _employee table (the prefix might vary, e.g., tb_employee). Click Browse and find your user account row, then click Edit. Under the passwd column, change the Function dropdown to MD5. In the Value field, type your new password. (the shop will now turn your new password automatically in a MD5 hash) Click Go at the bottom right to save changes. You can now log in to the admin panel. and you can also find help here: and

But you get this error with 'php collect module' very often in error logs: This occurs after an admin login and logout, when an item is subsequently searched for in the front office (at least, that is how I was able to reproduce the error). 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/controller/FrontController.php(1437): CartCore->update() #4 classes/controller/Controller.php(192): FrontControllerCore->init() #5 classes/controller/FrontController.php(264): ControllerCore->run() #6 classes/Dispatcher.php(858): FrontControllerCore->run() #7 index.php(33): DispatcherCore->dispatch() HTTP Request POST /de/index.php?controller=trigger&ts=1772887354

...once again, how to fix this with PHP 8.1 ? Please help @datakick Is that simply sufficient? in /controllers/front/TriggerController.php // BEFORE: trigger_error("Attempt to update unsaved object", 512); // AFTER: @trigger_error("Attempt to update unsaved object", 512);

Gibt es da 2-3 Stellen mit der Weiterleitung zu Polyfill (Frontend/Theme und Backoffice) oder? Beide male alles vom <script> entfernen? oder auf Cloudflare-Alternative umstellen falls du das wirklich noch brauchen solltest: https://cdnjs.cloudflare.com/polyfill/v3/polyfill.min.js?features=IntersectionObserver oder den Aufruf blockieren per .htaccess (bzw. sollte so das Ausführen verhindert werden, der Aufruf erfolgt dennoch): Header always set Content-Security-Policy "script-src 'self' 'unsafe-inline' 'unsafe-eval'; script-src-elem 'self' 'unsafe-inline'"

Hi, in 1.6 ist das Backend unverändert (ja die Werbung ok..., damit muss/kann man leben oder eben sponsoren). Hast du die Shopinstallation direkt von hier oder über einen "Service" / Hostinganbieter durchgeführt, das ist nämlich dann meistens die reinste Katastrophe (Softaculous usw.) ? Hilft es, wenn du eine andere Bildvorschau auswählst? Ggf. wäre das die kurze Abhilfe, dann mach ein Update auf 1.6 👍

We’ll probably have to get used to this well-crafted type of spam. AI can do that.

In that case, screenshots wouldn't be helpful. We have them as standard and have only really integrated the logo well. By "adjustments," I meant technical ones, like placeholders or modified uses for standard themes (such as notifications about partial deliveries). We use a third-party theme for the shop and the relatively clean standard emails are quite suitable for it (thankfully).

A good idea, especially if you use multishops. Then your idea/module is actually absolutely necessary. For multi-shops, I have to honestly say that I would prefer to have two of my own installations. I support the idea (but we don't have a multishop). For us, we use the standard email themes, but some of them have already been heavily modified to suit our needs.

Yes, I understand, thank you for your detailed answer! But not every customer can have their own server; just think of the environmental impact. The biggest problem, in my opinion, is administration. A dedicated physical server is a huge security issue, and very few people can adequately secure and maintain it daily. And very few want to pay professionals... VPS (virtual private servers) would be a better solution; they're also available managed. There are plenty of providers that offer sufficient performance, including hosting services.

I'd really like to know what database size we're talking about here? Are you planning to import a database, or what exactly are you doing? Generally speaking, this isn't a real problem anymore, even on shared hosting. I know some excellent providers where you don't have these issues and it still only costs a few euros a month.

ok scheint also besser zu werden... schaue unbedingt die Länder durch etc. und "ändere" vielleicht einen vorhandenen Mwst.-Satz, statt neu anzulegen, das musst du einfach mal probieren. Wie gesagt hatte ich da nie Probleme bei tb. Suche dir auch mal "alte" Forumsbeiträge (auch von Prestashop) über das Modul Europäische Rechtssicherheit, das war am Anfang recht kompliziert und fehlerhaft bzw. musste man eine Reihenfolge beachten für die Mwst., sonst hat das nicht funktioniert wie es sein sollte. Das für tb sollte nun aber fehlerfrei sein. Zum Thema Installation: ich hatte testweise ein einziges mal versucht, tb über so einen Softwaredienst aufs Hosting zu installieren (Softaculous) - nie wieder, war total buggy.

Lokalisierung > Steuersätze und Steuerregeln einstellen, alles nicht benötigte rausschmeissen bzw. einfach abändern zu 7 und 19% oder was bei dir eben zutrifft. Wenn du an Endkunden im Shop verkaufst, darf da nicht "zzgl. MwSt." stehen, die Preise müssen INKL. MwSt. angegeben werden, das ist dir sicher bekannt. Es scheint auch das Modul Europäische Rechtssicherheit nicht aktiv zu sein. Das brauchst du, teilweise wegen der MwSt.-Einstellung und auch daß der Hinweis "zzgl. Versandkosten" (oder eben was anderes) angezeigt wird, was auch vorgeschrieben ist. Handelst du hauptsächlich in Deutschland? !! vorher aber ggf. die Länder richtig erstellen wohin du liefern magst bzw. Gebiete daraus erstellen (EU, Schweiz, USA bspw., das wird dann jeweils anders behandelt und du kannst auch einstellen ob du bspw. für USA die deutsche USt. erheben willst auch wenn netto geliefert werden würde, denn da gilt kein USt-OSS). Die USA sieht also dann die Preise brutto wie in DE. Die richtigen Ländereinstellungen sind extrem wichtig.

hast du mal einen Screenshot o.ä.? ich verstehe das nicht ganz und konnte auch keinen derartigen Fehler feststellen, auch in anderen Versionen nicht. Hast du das EU-Modul aktiv?

Thanks for your contribution. I don't want to discuss here whether a particular approach is the right one. Only time will tell, and then the next few weeks when the law is in effect. However, all the statements I've found so far point in this direction: The cancellation function must be accessible even without logging in. We must also not forget that we are viewing this strongly from the perspective of a shop owner... So it wouldn't be as most people here seem to think. It remains a nonsensical approach, and of course, it annoys the shop owner to varying degrees 🙂

@Yabber You don't need to explain it to me; I think all shop owners here know the procedure. But you should understand what's required and implement it—that's just how it is. Whether it makes sense at the moment or not. If you ever get prosecuted for such a violation (e.g. GDPR, Withdrawal button or anything similar), you'll have to explain it to the authorities, and maybe then they'll understand and take notice. Excuse my language, but this isn't getting us any closer to a solution.

Here's a statement from the trade association (a specialized lawyer provided information on this). I'm including the German text here so you can use a translation yourself. I think this conveys the information most accurately. I'm really having doubts about the login issue. Durch den Widerrufsbutton soll sichergestellt werden, dass Verbraucher einen Vertrag ebenso leicht widerrufen können, wie sie den Vertrag abschließen konnten. Die Ausübung des Widerrufsrechts soll nicht aufwendiger sein als das Verfahren für den Vertragsabschluss. Der Widerrufsbutton muss für registrierte Kunden und nicht registrierte Gastbesteller bereitgestellt werden. Die Widerrufsfunktion muss grundsätzlich auch ohne Login erreichbar sein. Die gesetzlich vorgeschriebene vierzehntägige Widerrufsfrist läuft jedoch erst ab Erhalt der Ware und somit kundenindividuell. Laut dem Gesetzentwurf reicht es aus, wenn die Widerrufsfunktion ohne Rücksicht auf die individuellen Widerrufsfristen pauschal angezeigt wird. Ist das Widerrufsrecht des Verbrauchers für einen bestimmten Vertragsgegenstand erloschen, wird es durch die Bereitstellung eines Widerrufsbuttons durch den Unternehmer auf seiner Website nicht wieder aktiv. In der Regel wird den Vorgaben dadurch entsprochen, dass der Widerrufsbutton deutlich beschriftet wird, beispielsweise mit „Vertrag widerrufen". Der Button ist optisch hervorzuheben (z. B. Farbwahl, Kontraste) und muss auf der Hauptinternetseite verfügbar sein. Dabei ist er eindeutig von anderen Informationen wie den AGB, dem Impressum oder der Datenschutzerklärung abzugrenzen. Nach dem Klick auf den Button (auf der Hauptseite) ist der Verbraucher zunächst auf eine separate Seite weiterzuleiten, auf der er bestimmte Vertragsinformationen eingeben und dann eine weitere Schaltfläche, z.B. „Widerruf bestätigen“, anklicken muss, um den Widerruf zu erklären. Bei den Vertragsinformationen (damit der Widerruf dem richtigen Vertrag zugeordnet werden kann) ist folgendes abzufragen: Name des Verbrauchers Daten zur Identifizierung des Vertrags (z. B. Bestell-, Auftrags- oder Vertragsnummer) Angaben dazu, wie der Eingang des Widerrufs bestätigt werden soll (in der Regel per automatisierter E-Mail). Der Widerruf ist also samt Inhalt der Widerrufserklärung sowie Datum und Uhrzeit des Eingangs zu bestätigen. Wurden mehrere Verträge abgeschlossen oder umfasst der zu widerrufende Vertrag mehrere Waren oder Dienstleistungen, so muss der zu widerrufende Vertrag oder Vertragsteil vom Verbraucher konkret benannt werden.

Hi, "Länder" > MwSt. anzeigen und seit dem Modul "Europäische Rechtssicherheit" funktioniert doch eigentlich ganz gut?! Mehr Infos bitte... auch wenn die MwSt. enthalten ist musst du ja für Endverbraucher den Hinweis geben. Ich habe im o.g. Modul aber auch eine Anpassung machen müssen, war aber eher optischer Natur fürs Theme. Ist es bei dir ggf. auch fest im Theme inkludiert? Dann kannst du es auch per Übersetzung lösen, aber Warenkorbmodul usw. muss dann auch dazu passen.

Okay, I also think that's an exaggeration just because you haven't seen any activity for x weeks. A project like this isn't so short-lived that it needs an update every week. Many developments certainly require several weeks of work or even longer, especially if you're not doing ThirtyBees programming full-time. The internet and everything connected to it is fast-paced, that's clear. But the rule still applies: if you're in a hurry, go slowly. It's nice to get an update from Acer, even if it doesn't bring anything new.

Hi, I understand your concerns. Generally, I still see great potential in Thirtybees. It's just perhaps not being fully realized. It's also difficult to break into such an environment. Either you have good programmers or you have good salespeople. It seems you don't have both, or, as is so often the case, the team fails. But I also understand your concerns, and of course, Thirtybees currently carries a lot of baggage at its core. We know where it comes from... and yes, to lead it into the future, a thorough overhaul would be necessary. But please, no symfony-style strategy 😞

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.

I've also come to the conclusion that we're talking about different things. On the one hand, there's the simple cancellation "I don't want the goods / I want to return them," and on the other hand, there's an automated process with a possible automatic refund. These are indeed different things, and the EU regulation doesn't require any refund function. The conditions for a refund are fully and clearly regulated elsewhere, and have been for a long time; there won't be any changes to that in June 2026. And we certainly don't use a shop system for this, but rather an inventory management system, which undoubtedly operates on a different level. But thank you for the hint to keep our business going. Now nothing can go wrong. 🤙 🤠

@vir and @Yabber: The simplest form has three lines: name, email address, order number, and a text field for free-form comments if the customer wishes to provide them. And nothing is automatically pulled from the shop data in the simplest version. Submit button – done. Does it really take an hour to fill it out? Is there anything about it that isn't GDPR-compliant? I completely understand the need for a more sophisticated solution, but I don't quite understand why other opinions aren't being understood. Some people are interpreting the EU regulation to mean that a login wouldn't be a problem. We're not there yet, folks. At worst, time will tell. There's plenty of written guidance on implementation, based on the current assessments from lawyers and trade associations. We don't manage inventory, packing lists, invoices, etc., in the Thirtybees shop. The shop system is simply the customer frontend for us. All orders are transferred to our inventory management system, where everything else is handled, including picking in the warehouse, label printing, etc. Perhaps the requirements are simply too different. But it's good that we're discussing it, and I think the topic will become more prominent in this forum in the near future as more people look for a solution.

ok, so you are fine. It´s not my idea. The regulation says in point 37 regarding implementation: ....For example, the consumer should not have to undertake procedures to find or access the function.... So again my question: is a login an additional "procedure" to access this function? Please answer this question for yourself. In my opinion, it's at least one more step than simply clicking the first button or link, so it is. But perhaps we simply have to wait until June to see how this plays out. In Germany, we have the specific problem that lawyers can send out cease-and-desist letters, which are very expensive. This isn't the case in all countries, so perhaps that's why you're not so sensitive about it. Yes, unfortunately, this makes us very "anxious" in Germany, and online shop owners are often treated like serfs.

I understand if you want to support the module for your own reasons... but that's no reason to be so pushy. As already mentioned, requiring a login could be seen as a hurdle > it's not entirely clear yet; time will tell. However, I don't want to be a guinea pig and have to pay for it. 🙂 The explanations in point 37 of the regulation provide further clarity regarding implementation: ....For example, the consumer should not have to undertake procedures to find or access the function.... Is a login a "procedure" to access this function? Please answer this question for yourself. I just find it problematic to offer a module that might not take this into account and tells the customer it's 101% compatible with the regulation, because I don't think it is or it is not clear yet. But it's everyone's own decision. We'll probably find different solutions, and that's why we're here, not to quarrel.