Yabber

In the language configuration: Localization -> Languages, add your own “No-picture” images (can be transparent PNG).

A less labor-intensive solution is to replace the image /img/404.gif with an blank transparent image.

I deliberately deleted the image for this one category to get the effect of displaying a placeholder image 🙂 Whether this is a bug or not is open to debate. If we decide to display subcategory images, we should add images to all categories. However, many stores do not have a uniform data management concept and add images to some categories but not to others. And with these placeholder images, it looks ugly.

Displaying a placeholder image for subcategories causes an bug in getSubCategories() method of Category class: foreach ($result as &$row) { $row[‘id_image’] = $row[‘id_category’]; $row[‘legend’] = ‘no picture’; } Whether the image exists or not, ‘id_image’ with the ID of the given subcategory is always returned. And if there is no image, the rules from htaccess load a placeholder image.

As for a descriptive list of changes for version 1.7.0, it does not exist yet, because this version is still under development. This is a programming list of changes: https://github.com/thirtybees/thirtybees/compare/1.6.0...main Without knowing which module you are using to create these articles, it is difficult to say anything.

Since you're already spending time on upgrades and testing, it's best to upgrade thirtybees to 1.7.0 (Bleeding edge) and enable PHP 8.3.

It is not just a matter of module compatibility with a given version of Prestashop. This module is based on the SaaS model and requires the “ps_accounts” module to be installed and the store to be integrated with Prestashop servers. Soon, you will have to pay a subscription fee to use these modules, and if you don't pay, Prestashop will be able to disable any modules it wants in any store it wants.

Personally, I think Turnstile is MUCH better than Google reCaptcha. It's also worth considering changing your anti-spam security.

Not all stores use Clodflare. The module from the thirtybees repository “nocaptcharecaptcha” also secures the customer registration form.

This module has bugs, and this response from the module developer makes no sense. It's easy to verify. Just write a product review or log in to your customer account. Then check the tab: Customers -> Shopping Carts. No shopping carts are created from writing comments or logging in. In the Cart thirtybees class, there is no such thing as an "abandoned cart", so there can be no bug in something that does not exist. Whether a cart is abandoned or not is only classified by modules using their own methods.

Modules on Prestashop add-ons have new versions every few moments because these modules contain millions of bugs and are constantly being fixed.

The Stripe module for thirtybees supports credit cards and iDEAL payments.

At the bottom of page, JavaScript scripts are loaded, preceded by comment: /* <![CDATA[ */

https://github.com/thirtybees/blockviewed It also collects product data from cookies. After all, this module has no value for customers, so why install it in the store?

I have never encountered a carrier module for Prestashop that would provide such detailed information about shipments via API. Not even from such giants as UPS, FedEx, or DHL.