e-com

This is not a bug just sloppiness in making of modules. Modules registered hooks for which they do not support these hooks. In Modules -> Positions, you can safely unhook these modules from these hooks.

Administration -> Preferences Check "Upload quota" settings.

Not order.php but Order.php After adding override file, delete the /cache/class_index.php file

Link in the content is correct. https://github.com/thirtybees/psonesixmigrator/releases/tag/2.1.1 You should download the file psonesixmigrator-v2.1.1.zip

This is a prestashop bug fixed in thirty bees. In multishop option, installing a new theme for other stores would mess up the image formats of other themes.

There is a free migration module for prestashop 1.6. https://thirtybees.com/migrate-from-prestashop/

Now it's OK. That's by the way, PHP 8.2 compatibility can be improved. Message: Creation of dynamic property AdminCoreUpdaterController::$total_cache_size is deprecated Location: classes/controller/Controller.php line 173 Message: classes/controller/Controller.php: Method ControllerCore::getController() is deprecated. Called from tools/profiling/Tools.php:109 Location: classes/Tools.php line 1456

I tested cache with Redis Server. There is a fatal error when profiling is enabled: *ERROR* Error: Cannot instantiate abstract class Db at line 679 in file classes/db/Db.php *ERROR* Fatal Error: Uncaught Error: Cannot instantiate abstract class Db in /home/ecom/public_html/tbtest/classes/db/Db.php:679 Stack trace: #0 /home/ecom/public_html/tbtest/classes/db/Db.php(632): DbCore::createInstance() #1 /home/ecom/public_html/tbtest/classes/Configuration.php(440): DbCore::getInstance() #2 /home/ecom/public_html/tbtest/classes/Configuration.php(406): ConfigurationCore::loadConfiguration() #3 /home/ecom/public_html/tbtest/classes/error/response/ProductionErrorPage.php(50): ConfigurationCore::get() #4 /home/ecom/public_html/tbtest/classes/error/response/AbstractErrorPage.php(43): Thirtybees\Core\Error\Response\ProductionErrorPageCore->renderError() #5 /home/ecom/public_html/tbtest/classes/error/ErrorHandler.php(125): Thirtybees\Core\Error\Response\AbstractErrorPageCore->sendResponse() #6 /home/ecom/public_html/tbtest/classes/error/ErrorHandler.php(115): Thirtybees\Core\Error\ErrorHandlerCore->handleFatalError() #7 [internal function]: Thirtybees\Core\Error\ErrorHandlerCore->uncaughtExceptionHandler() #8 {main} thrown at line 679 in file classes/db/Db.php

Prestashop 1.6 is only compatible with PHP 7.2, and there are still a lot of incompatibility errors with PHP 7.4 in this fork by Eolia.

I see on github, that a lot of modules have already been patched. I have a request to pick up module version, so that their updates will happen and not to do the same job twice.

This is what I found interesting: https://eoliashop.com/prestashop-new I have installed for testing on localhost. There are a lot of bugs on PHP 7.4, and it is completely incompatible with PHP 8. But there are a few interesting solutions to implement into thirty bees. Or maybe someone knows this guy Eolia and can persuade him to join the thirty bees project, rather than agonising over prestashop himself 🙂

PHP 8.2 stable is already released, then testing can begin 🙂 But PHP 8.2 for Core Updater would be useful.

If this "other" field is to be separately displayed somewhere by itself, then make such a modification: 'other' => $invoiceAddress->other And in template variable: {$other}

Nothing needs to be modified. Add "other" field to the Address format.

Transition from PHP 7 to PHP 8 is quite a revolution, and this Panda template is an antique made for TB 1.1.0. A template is not only the template itself but also probably several or more modules installed together with the template. And it's unlikely any of them are compatible with PHP 8. It should be up to developer, who sells the template, to have an up-to-date product. Also, in my opinion, it's best to write to ST-THEMES to take some time and make an update of their template to TB 1.4.0 with PHP 8.

Example modification of a blocklayered module: https://github.com/thirtybees/community-theme-default/compare/1.1.x...e-com-presta:community-theme-default:colapse-module Analogously, it can be applied to other modules.

Square category images. 1. In Preferences -> Images, change medium format to 360px X 360px. 125px X 125px is too small. 2. In all categories, add 360x360px square images as "Category thumbnail". 3. In module configuration, select medium format. 3. And the end result:

In module configuration, you can choose which image is displayed. And only what is created in the image preferences is available for selection:

I have added this type of module to download: https://forum.thirtybees.com/topic/5933-free-module-categories-on-homepage/

Module displays categories with images on the homepage. Module compatible with WebP and lazy load. Download URL: "Categories on homepage"

What are the plans for SwiftMailer, whose project has been closed? Are there plans to migrate to Symfony Mailer?

Very old these news on dashboard 🙂

This is very logical. Warehouse prints delivery-slips and packs shipments, and then shop staff adds new products to orders. And we have something different in shipments and something different in orders.

And an official module compatible with PS 1.6 can't be? https://addons.prestashop.com/en/payment-card-wallet/52036-square-official-sell-online-and-in-store.html#overview

Qloapps is not one module for PS 1.6. It is thousands of modifications to the PS 1.6 engine.