All Activity

For such simple errors you can always check with ChatGPT: As @yaniv14 said, his fix will most probably fix your error. In future please give the complete code that Collect PHP Logs gives. This helps greatly for developers that know what to look for to assist you. 😉 (of course obfuscate any sensitive info as your true local address, admin folder, etc.) Sample how the code works when you simply copy and paste it here: Exception Message: ThirtyBeesException: Property Product->price is empty Location: classes/ObjectModel.php line 1054 Stacktrace #0 classes/ObjectModel.php(1054) #1 classes/ObjectModel.php(333): ObjectModelCore->validateFields() #2 classes/ObjectModel.php(361): ObjectModelCore->getFields() #3 classes/ObjectModel.php(610): ObjectModelCore->getFieldsPrimary() #4 classes/Product.php(7816): ObjectModelCore->add() #5 controllers/admin/AdminProductsController.php(822): ProductCore->add() #6 classes/controller/AdminController.php(597): AdminProductsControllerCore->processDuplicate() #7 controllers/admin/AdminProductsController.php(1341): AdminControllerCore->postProcess() #8 classes/controller/Controller.php(202): AdminProductsControllerCore->postProcess() #9 classes/Dispatcher.php(865): ControllerCore->run() #10 adminXXX/index.php(58): DispatcherCore->dispatch()

But these two lines are identical

2.7.2 - 03/23/2025 Improved flow. Improved category display. 2.7.1 - 11/09/2023 Fixed a bug when updating to module version 2.7.0. 2.7.0 - 10/28/2023 Images replaced by icons to lighten loading. Added compatibility with PrestaShop 8. PHP 8.1 support. Improved display of information messages when validating module configuration. Last export date added to table showing XML flow files. Withdrawal of compatibility with PrestaShop 1.5.

2.7.2 - 23/03/2025 Amélioration du flux. Amélioration de l'affichage des catégories. 2.7.1 - 09/11/2023 Correction d'un bug lors de la mise à jour vers la version 2.7.0 du module. 2.7.0 - 28/10/2023 Remplacement des images par des icônes afin d'alléger le chargement. Ajout de la compatibilité avec PrestaShop 8. Prise en charge de PHP 8.1. Amélioration de l'affichage des messages d'information lors de la validation de la configuration du module. Ajout de la date du dernier export dans le tableau présentant les fichiers de flux XML. Retrait de la compatibilité avec PrestaShop 1.5.

in this single example you sent I think changing: 'context' => (Configuration::get('PS_MULTISHOP_FEATURE_ACTIVE') == 0) ? 1 : ($this->context->shop->getTotalShops() != 1) ? $this->context->shop->getContext() : 1 to 'context' => (Configuration::get('PS_MULTISHOP_FEATURE_ACTIVE') == 0) ? 1 : (($this->context->shop->getTotalShops() != 1) ? $this->context->shop->getContext() : 1) would do the trick

https://www.php.net/manual/en/migration74.deprecated.php

@datakick I get the attached error when trying to upgrade the php from 7.4 to 8.3. I understand that it is a probem with a module in the theme. There is perhaps more but must test to start somewhere and see if it is possible Any hints please, shop_error.txt

Thanks a lot for this new feature! It will be very helpful. Something similair was on my ToDo list as well 😏 I will have break in early april. Afterwards I will update our system to new PHP version and will also upgrade again to bleeding edge. Then I can test it with my live site 🤩

Yea I did decrypt it but attached wrong file

That's not really relevant to this thread. Feel free to create a dedicated topic to discuss that

There are a lot of use cases, but I guess it depends on what needs you have. For example, we have recently used this feature to find all products within certain profit margin range.

For future reference, it's pointless to attach encrypted error messages. You are the only one who can decrypt it -- you need to log in to your back office, go to Logs, and there you can upload this encrypted file. It will show you the error message.

Problem Solved. Curl was not installed on the new server for some reason

@datakick Someone can interpret this decrypted 500 error. Se attachment exception_202532217170.txt

I'm still waiting for slider option for this module "Block Layered navigation". Is this ever gonna happen ?

Interesting possibility, I don't have a use for it that I can think of yet, but as always, thanks for your work and i will test it!

3.7.0 - 03/10/2025 Anti-spam protection on newsletter registration form for PrestaShop versions 1.7 and higher Improved registration blocking to combat new forms of spam attacks

For developers here: you can test adding your own filter fields by modifying Admin***Controller classes, using new property filters_list. This property accepts the fields in the same format as property fields_list (which is used to define list columns) Example from AdminOrdersController: This is all that is needed to support filtering on customer email and names: https://github.com/thirtybees/thirtybees/blob/f59054511624de2131f86e4373604f827362468e/controllers/admin/AdminOrdersController.php#L214-L230 $this->filters_list = [ 'customer_email' => [ 'title' => $this->l('Customer - Email'), 'type' => 'text', 'filter_key' => 'c!email' ], 'customer_first_name' => [ 'title' => $this->l('Customer - First Name'), 'type' => 'text', 'filter_key' => 'c!firstname' ], 'customer_last_name' => [ 'title' => $this->l('Customer - Last Name'), 'type' => 'text', 'filter_key' => 'c!lastname' ], ];

Hello everyone, I'd like to announce new upcoming feature, and as always ask for testing and reporting any and all issues, problems, and enhancement requests. This new functionality is names List Filters. You can test it by upgrading your store to list-filters branch (using core updater in custom targets) What this new functionality do? On every (filterable) lists in back office you will find a new icon in upper right corner: When you click on it, new section will appear. Here, you can define additional filters that will be applied to the list. The new filters are applied together with the standard filters from list header. But these new filters are slightly more powerful, because you can select operator - not, contains, starts with, between, any of Also, developers can define additional filters in AdminControllers that do not depend on list columns. For example, I have added new filter fields for Order list controller - (Customer - Email, Customer - First Name, Customer - Last Name). So you can filter order list by customer email, even though customer email is non one of list columns! We will be slowly adding more and more filter fields based on your suggestions. Let us know what you need!. This functionality is not 100% completed, but it's quite stable. I've been using it on few production servers without any issues for a few weeks now, so it should be safe for you to test it as well. We already have a few enhancement we want to implement. One of them is support for filter presets -- you will be able to save your filter settings, and easily switch between different presets. Now it's your turn. Please test and give feedback. I'm sure there is a lot to improve here. I'm very excited about this new feature, as I wanted to do have this for a few years now. And finally it's coming 🙂

Thank you for this. I've commented on your PR and requested some changes. Could you look into that?

I modified the module to make it work properly in multishop mode: https://github.com/thirtybees/tbhtmlblock/pull/10

You have a PM.😸

Stacktrace #0 builtin #1 classes/ObjectModel.php(752): trigger_error("Attempt to update unsaved object", 512) #2 classes/Cart.php(2809): ObjectModelCore->update(false) #3 classes/controller/FrontController.php(1437): CartCore->update() #4 override/controllers/front/CartController.php(86): FrontControllerCore->init() #5 classes/controller/Controller.php(192): CartControllerCore->init() #6 classes/controller/FrontController.php(264): ControllerCore->run() #7 classes/Dispatcher.php(858): FrontControllerCore->run() #8 index.php(70): DispatcherCore->dispatch()

The corresponding code comes from ObjectModel: /** * Updates the current object in the database * * @param bool $nullValues * * @return bool * @throws PrestaShopDatabaseException * @throws PrestaShopException */ public function update($nullValues = false) { $id = (int)$this->id; if (!$id) { trigger_error("Attempt to update unsaved object", E_USER_WARNING); return false; }

Hello, After the shop migration is done, I am still figuring out some minore issues. One is the following kind of error log entries: [15-Mar-2025 17:57:19 Europe/Zurich] PHP Warning: Attempt to update unsaved object in /home/codium/public_html/maxmalt.ch/shop/classes/ObjectModel.php on line 752 [19-Mar-2025 13:38:16 Europe/Zurich] PHP Warning: Attempt to update unsaved object in /home/codium/public_html/maxmalt.ch/shop/classes/ObjectModel.php on line 752 When I search the server logfiles, this kind of HTTP request machtes with the timesamps. [15/Mar/2025:17:57:19 +0100] "POST /?rand=1742057839489 HTTP/1.1" 200 171 "https://maxmalt.ch/glen-scotia-1992-23y-hart-brothers-finest-collection-50-5-scotia-1992-hb-283.html" "Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.3 Mobile/15E148 Safari/604.1" 2a02:26f7:e344:5444:0:72b0:2cff:6faf - - [15/Mar/2025:17:57:19 +0100] "POST /index.php?controller=trigger&ts=1742016985 HTTP/1.1" 200 43 "https://maxmalt.ch/glen-scotia-1992-23y-hart-brothers-finest-collection-50-5-scotia-1992-hb-283.html" "Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.3 Mobile/15E148 Safari/604.1" [19/Mar/2025:13:38:16 +0100] "POST /index.php?controller=trigger&ts=1742387892 HTTP/2" 200 43 "https://maxmalt.ch/glen-scotia-1992-23y-hart-brothers-finest-collection-50-5-scotia-1992-hb-283.html" "Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.3.1 Mobile/15E148 Safari/604.1"