DRMasterChief

An up-to-date PayPal module would obviously be a huge deal 👍 We use the instant payment method, not "funds on hold." We also don't offer installment payments or payment on invoice via PayPal.

I’m not using the Warehouse theme, but something else. I’ve started a new thread for a module that should work with any theme.

Ich wollte das Thema schema.org / Breadcrumbs noch einmal aufgreifen. Dabei bin ich auf das alte JSON-Modul von 2024 gestoßen (es wird scheinbar nicht mehr weiterentwickelt). Ich bin auf diesem Gebiet kein Experte – SEO und Ähnliches haben für uns bislang keine große Rolle gespielt. Ist das ein Thema, das die Shopbetreiber hier interessiert, oder wie geht ihr damit um? Ich habe dafür ein Modul entwickelt, das die von Google geforderten Pflichtfelder einwandfrei übermittelt.

wir sind hier ja im deutschen Forum: Ich wollte das Thema Breadcrumbs noch einmal aufgreifen. Dabei bin ich auf das alte JSON-Modul von 2024 gestoßen (es wird nicht mehr weiterentwickelt). Ich bin auf diesem Gebiet kein Experte – SEO und Ähnliches haben für uns bislang keine große Rolle gespielt. Ist das ein Thema, das die Shopbetreiber hier interessiert, oder wie geht ihr damit um? Ich habe dafür ein Modul entwickelt, das die von Google geforderten Pflichtfelder einwandfrei übermittelt. I wanted to revisit the topic of breadcrumbs. In doing so, I came across the old JSON module from 2024 (which is no longer being developed). I’m no expert in this area—SEO and the like haven't played a major role for us so far. Is this a topic that interests the shop owners here, or how do you handle it? I’ve developed a module for this that flawlessly transmits the mandatory fields required by Google.

To remove the gender (social title) field from the customer registration form in thirty bees, you must edit your active theme’s Smarty template file (identity.tpl or authentication.tpl), as thirty bees does not feature a single toggle switch for this in the back office. Editing the Theme Template File: Open your site files via FTP or your hosting file manager. Go to your active theme directory: /themes/your-theme/templates/customer/ or /themes/your-theme/ depending on your specific theme structure. Look for files related to customer registration and account creation, primarily authentication.tpl, identity.tpl, or order-opc-new-account.tpl (and/or also removing the sections from files order-opc-new-account.tpl and order-opc-new-account-advanced.tpl, override/controllers/front/AuthController.php) Find the block of code handling the gender radio buttons or select dropdown, which usually looks like: smarty<div class="clearfix"> <label>{l s='Social title'}</label> <!-- gender radio buttons code --> </div> Comment out or delete this section from the files. Clear your thirty bees compilation cache under Advanced Parameters > Performance in your back office so the template changes appear live. You can also do a search in database e.g. like this: ALTER TABLE `ps_customer` DROP COLUMN `id_gender`; ALTER TABLE `ps_address` DROP COLUMN `id_gender`; to find all files. We have deleted it since a few years, it is hardcoded in our theme and deleted, no problems but i do not have a good Readme about this 🙂 and this one: Warehouse Theme Working - Page 3 - Theme Compatibility - thirty bees forum

maybe the best way in this situation to get off all the rubbish 🙂 well done!

Since yesterday/today, there has been a notification regarding an update for the PayPal module. When you update it, you get a message stating that it is outdated/deprecated. Okay team @Acer, it’s time for more information. PayPal is extremely widespread and used by practically every merchant and customer alike. How do we proceed?

To be honest, you’d have to try it out. I didn't have an eye on ASM. We don't use any inventory management within the shop itself; instead, we use separate software in the office and warehouse.

Thanks for the `tbchangecarrier.zip` module; I’ve taken a quick look at it. Fundamentally, it serves a different purpose: `tbchangecarrier`: Actually changes the order's shipping carrier in the database - updating `id_carrier` in both the `order_carrier` and `orders` tables. It does not send an email to the customer; it is purely a silent correction made in the backend. My module, designed for our specific requirements, does not alter the order data at all; it simply provides the option to send the customer a different (additional) tracking email containing a different tracking link. It uses a hook to integrate into the order overview page in the backend, providing a dropdown menu for shipping methods and a field for the tracking number. Once the details are entered and submitted, the customer receives a shipping notification containing the correct link. The reason for this is that we often handle both very light and very heavy packages sometimes within a single customer order. 0.5 kg package is shipped via DHL using the native tracking link in the backend. 35 kg package is shipped via DPD using the "new" tracking link in the backend, which points to DPD tracking. However, the customer cannot actively select DPD shipping in the shopping cart at all. That is the reason why I included this information in this topic. After all, there are -so to speak- "multiple" tracking numbers involved, and this allows any number of shipping emails to be sent to the customer (for example, even for 10 packages...).

Thanks for the info - but that’s not really an issue here on the forum, nor regarding the technical feasibility. If such conditions or rules exist in a given country, each dealer is personally responsible for compliance—that goes without saying. Contractual terms can also be agreed upon online (in Germany, these are known as General Terms and Conditions), and a dealer could certainly address this there before the contract is concluded. Let’s continue discussing the "technical" side of things.

Is anyone else working on this? I’m currently creating a module that allows the admin to select from various shipping carriers, so the customer receives the correct tracking link (regardless of which carrier they chose at checkout). We run into this situation sometimes because packages can't always be shipped via DHL, so we have to use a different carrier. However, the customer needs to receive the correct tracking number with link; otherwise, Thirty Bees simply uses the standard link for the selected shipping method and appends the tracking number (then it goes wrong).

Hello, no, I haven't pursued that any further at the moment.

Claude Sonnet w/wo Codex is about 4 times better for coding than ChatGPT, especially for PHP fixes and .tpl The threadopener should give them a try, you can prompt various tests and use all this new code in a testshop. Also Qwen Coder is very impressive.

any Cronjob active?

Great, thank you for this fast fix, i already use it. The biggest problem is that the error cannot be reproduced. It is also unusual because it occurs extremely rarely. However, we regularly experience issues with orders from Ireland—though without the error message—yet the problem is similar (the order is not created). Do we have to change the others too? if ($this->context->cookie->logged) { $idCustomer = PaypalCustomer::getPayPalCustomerIdByEmail($email); if (!$idCustomer) { $ppc = new PayPalCustomer(); $ppc->id_customer = $this->context->customer->id; // ⚠️ $ppc->paypal_email = $email; $ppc->add(); } $customer = $this->context->customer; // ⚠️