DRMasterChief

I'm not entirely sure, but you might be able to change the email address in the database to one that definitely works, and then use the "forgot password" function on the back-office login page. Come on, we're going to end up with a complete guide here 🙂

@Madhosh i think you should urgently install the module in BO: Mail via phpmailer v.1.1.1 (this is the new module for E-mail transport and you need this)

What’s your take on additionally securing the admin page with an .htpasswd file? (regardless of everything else) I think it's great that there is an official script that is user-friendly and also prevents the simple replacement of access credentials in SQL. Thanks!

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...: BEWARE - THIS DOES NOT WORK WITH tb >1.5.1 ANYMORE!! SEE NEW OPTION BELOW!! 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.