Yabber

The 'mailalerts' module passes the {message} variable to the template email 'new_order' sent to the store admin. Check in this email template if you have such a variable.

Looking at your store https://bountyhuntertoys.com/store/ it is clear to me that absolutely NOTHING in this store has been configured. Starting from such basics as enabling friendly URLs or anti-spam protection of the contact form. Also switching to a paid SaaS might be a good option, pay $300 a month, then at least the basic configuration will be done for you by shopify support. As for migration, exporting data from thirtybees to CSV will not help you at all. You need to be very knowledgeable about the database structure of both applications to properly map the data. Also, it is best to pay a few hundred dollars and have the migration done by a company that will do it properly. For example, Cart2Cart: https://www.shopping-cart-migration.com/provided-services/data-migration-service-packages And such a note that the migration does not transfer customer passwords, also all your customers will have to reactivate their accounts.

@DRMasterChief In blockcart.tpl template, change: {assign var='free_ship' value=count($cart->getDeliveryAddressesWithoutCarriers(true, $errors))} to: {assign var='free_ship' value=count($cart->getDeliveryAddressesWithoutCarriers(true))}

@the.rampage.rado The order of attribute combinations in the product configuration has no meaning. If I change the “Position” in the attribute values then the order on the store front changes identically.

I checked on TB 1.6 and sorting attribute values in BO by “Position” also works correctly on the front end on the product page.

@DRMasterChief The code you provided in the first post is about features, not attachments. And can't you use this futures functionality to present this additional product data? Instead of making some weird modifications to the attachments functionality.

Is it possible that we configure a different server and SMTP account in the module than we have in the “Mail via PHPmailer” module and the module uses those settings to send its emails?

Domain is let go by cloudflare, and cloudflare caches static resources for a long time. We should clean cloudflare's cache after changes to the site.

And I don't see any blocking by google: https://search.google.com/test/rich-results/result?id=M20EMayXf6pc4Bni8FkF7A&hl=pl

SwiftMailer is no longer supported and developed: https://github.com/swiftmailer/swiftmailer

There are a lot of modules for prestashop with security vulnerabilities: https://security.friendsofpresta.org/ Before installing any module, you need to check it for security vulnerabilities.

It's not about email marketing modules but about mail transport module. Install and configure the "Mail via PHPmailer" module.

php7.4-xml is a package of several modules. This package provides the DOM, SimpleXML, XML, and XSL module(s) for PHP. And what does phpinfo() say? Do you have the SimpleXML module loaded?

This is not possible, it would require a very serious modification of the thirtybees engine. And it would cause serious problems in the operation of the store, because, for example, all electronic payment gateways require customer address data. Only bitcoin payments can be anonymous.

Install Lua module to nginx, you will have nginx with htaccess support: https://github.com/e404/htaccess-for-nginx?tab=readme-ov-file

@wakabayashi From my tests, it seems that for AVIF format, Imagick gets better compression, and for WEBP format, GD library has better compression. It might also be worth adding support for Imagick to ImageManager class?

On prestashop addons there is a version 4.5.4 for PS 1.6.1 https://addons.prestashop.com/en/payment-card-wallet/40307-mollie-payments.html I don't have a Mollie account and I haven't tested it with thirtybees, well, and it's not clear how there with the compatibility of it with PHP 8.

Bleeding edge is a development version available as a repository on github: https://github.com/thirtybees/thirtybees And you could say that every day is different. You can perform an upgrade of your thirtybees to Bleeding edge by changing the Core Updater configuration:

@datakick After my tests of the latest version of "bleeding edge", I think that the support of system images in WEBP and AVIF formats already works very nicely. However, I noticed that some native modules have their own limitations when it comes to uploading image files. For example, the "homeslider" module: const ALLOWED_EXTENSIONS = [ 'jpg', 'jpeg', 'gif', 'png' ];

On the "Download Thirtybees" page in the "Server Requirements" section there is incorrect information misleading users who want to install Thirtybees.

And check still in Preferences -> Store Contact: "Shop email". As you have different email addresses in each place of configuration, then there are such problems.

In Customers -> Contacts you have the wrong mailing addresses.

Error 500 is a general server error that doesn't say anything. Look for the actual causes of the error in the "Error logs" of the "Collect PHP Logs" module.

This is the module: https://www.lineagrafica.es/en/modulos-prestashop/eu-cookie-law-banner-blocker-prestashop-module/

This module does not comply with current EU law, which requires a cookie manager installed, where the customer chooses which cookies to allow and which not to allow. So something like this: https://optlasers.com/