DRMasterChief

klingt ja schonmal cool, halte uns auf dem laufenden!

can´t wait for it - great. 🙂 👍

Due to email volume, reputation issues, and persistent problems with GMX and Hotmail (and all MS services...), we’ve been using brevo.com for the past few days (specifically for transactional emails). The setup process is fine; domain verification is quick and mandatory. However, the FAQ section is a bit outdated in places. It was important to us that the service be hosted within the EU. Their prices are lower than the provider you mentioned, though you’ll need to compare them yourself. Brevo.com doesn't strictly separate SMTP and marketing services, so you get everything bundled together in one package.

Hi, wenn du die Daten im Shop gut gepflegt hast (insbes. Gewicht etc.) könnte man damit ein kleines Modul für die (CSV-)Ausgabe bauen, die kannst du ja auch direkt an DHL übermitteln, da gab es doch mal einen Dienst der bei Verbindung dann "hört" ob Daten reinkommen und wenn, dann wird der sofortige Labeldruck angestossen (JTL macht es auch so).

Eine Lösung um die Grundpreisangabe auch in deutsch anzuzeigen. Die Werte sind ja im Backoffice hardcodiert in englisch und daher nicht einfach so bei den Übersetzungen möglich. Ich habe die product.tpl des Themes um folgendes erweitert, es wird entweder direkt die Bezeichnung abgefragt oder alternativ kann man auch mit "Anzahl der Zeichen" arbeiten. Wenn die Grundpreisangabe also bspw. in "Stück" ist, dann sind es 5 Zeichen, siehe Beispiel bei ==5 Hier mit einigen Beispielen, kann natürlich auf den jeweiligen Shop und die Grundpreisangaben angepasst werden: {if !empty($product->unity) && $product->unit_price_ratio > 0.000000} {math equation="pprice / punit_price" pprice=$productPrice punit_price=$product->unit_price_ratio assign=unit_price} {assign var='unity_display' value=$product->unity} {if $lang_iso == 'en'} {assign var='unity_len' value=$product->unity|count_characters} {if $product->unity == '1 qm'} {assign var='unity_display' value='1 sqm'} {/if} {if $product->unity == 'Auto'} {assign var='unity_display' value='Car'} {/if} {if $unity_len == 5} {assign var='unity_display' value='Piece'} {/if} {/if} <p class="unit-price"><span id="unit_price_display">{convertPrice price=$unit_price}</span> {l s='per'} {$unity_display|escape:'html':'UTF-8'}</p> {hook h="displayProductPriceBlock" product=$product type="unit_price"} {/if}

We are still using the existing PayPal module with thirtybees 1.6 on PHP 8.1, and without any problems!

Ah ok! Baust du auf einem vorhandenen Controller auf oder ist es ganz neu erstellt?

gut zu hören! magst du Screenshots von deinem Modul hier zeigen?

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);