Yabber

As for the “Guest Shopping” order mode, this option is not compliant with all EU directives on personal data protection and consumer rights: - the customer has no access to their personal data stored on the store's server, - the customer cannot edit their personal data, - the customer cannot submit a “right to be forgotten” request, - the customer cannot return purchased products (they must convert their guest account into a standard customer account). In addition, the “Guest Shopping” order mode is a terribly customer-unfriendly option. Customers have to laboriously fill in dozens of their personal and address details with every purchase. So if someone uses the “Guest shopping” mode in the store, they don't need the “Cancel order” button, because one more or less crime doesn't make a difference.

Canceling an order is not the same as returning an order - they are two completely different processes. A customer who has no information about their order is not a customer. Can you log into your bank account without any login information? You can't make this feature so that hackers from all over the world can cancel all orders in our store. This is my own module running on the displayOrderDetail hook - it is visible in standard customer and guest orders. The screenshot shows a simple configuration of the module. Of course, for orders that have the status “Order shipped” or “Delivered,” there can be no question of canceling the order. For such orders, the customer should make a standard return after receiving the shipment.

Such a leak of customer data could result in huge fines for Prestashop. This is probably why the previous owners sold Prestashop so quickly.

@DRMasterChief It won't be a "Cancel order" button, but a confusing contact form where the customer has to fill in dozens of pieces of information. This was certainly not the intention of the creators of this law. The customer clicks on the "Guest Tracking" link and sees a single "Cancel order" button, which changes the status of the order in the store to "Order canceled". And that's it.

Here is a description of the attack vector: https://www.prestashop.com/forums/topic/1105466-recent-prestashop-securtity-alert/?do=findComment&comment=3543558 Conclusion: Prestashop Addons Marketplace is a dangerous store where you should not provide any login details for your store. If you have provided your login details for your store on Prestashop Addons Marketplace, you should change them immediately.

The standard procedure in Prestashop is to release beta versions with thousands of bugs and security vulnerabilities for download as stable versions, and then fix these bugs in dozens of subversions. If stores do not update the engine and modules, they get hacked. There was a security vulnerability in PS 9.0.2, which was patched in the latest version 9.0.3. The basic order completion module “ps_checkout” used since PS 1.7 also had a vulnerability Here are all the security vulnerabilities detected in Prestashop and its modules: https://security.friendsofpresta.org/

I tested “Kustom Official” module on PS9 and WooCommerce. The module is designed as an aggressive virus. During the order finalization process, the module hides all other payment methods, presenting the customer with only the “Kustom” payment option. It is a terribly aggressive and intrusive way of fighting competition.

Cyber_Folks is owned by H88, a company that has been acquiring smaller hosting companies in Poland for many years. After each such acquisition, the prices of all services are raised by an average of 300%. Also, after this acquisition, Prestashop will be the most expensive SaaS in the world.

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.