the.rampage.rado

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()

You have a PM.😸

Yes, this is a must functionality for a serious shop but I'm afraid would be quite a big endeavor. Does your module allow to use 2 different couriers per order or it only passes one number to thirty bees and handles the rest outside the system?

In this version of the code - every change to the tracking numbers send out new email with the values you save, so your case would be OK - just add comma and the new number. Based on the poll there is no demand for this, possibly in future.

Nope, they should be filling gradually.

I would like to ask the community - do you (personally) need multiple tracking numbers per order? This does not solve the issue where you might have to use 2 different couriers (let's say you ship from 2 warehouses) but offers a solution with minimal impact - theme file should be changed, but example code will be given. Also tracked here: https://github.com/thirtybees/thirtybees/issues/1975 If somebody has a shipping module or CRM module that sets tracking numbers it would be nice to test this if it's backwards compatible fix as I don't have anything working with the webservice and there are couple of functions to fix in that aspect.

Making a new post as the screenshots are very annoying (or my way of doing them, idk...). Also should we create issues in github or report here if we find more stuff until this is in develpoment? 4. Packs don't subtract pack products when they are set up to. In this configuration: Purchasing a pack should subtract the pack's quantity per combination and each product's quantity in the appropriate combination. It does only subtract the pack's quantity and not the products'. The same is applicable for Decrement products in pack only. - if the pack is set at it - the quantities are not subtracted in each pack product.

Quick few things from me and I'm continuing testing this great addition: 1. Can we push "virtual attribute" option to the top as I think this will be the most used option from this list (I doubt packs with attributes will be made for just one combination of a product). We can rename this to 'all combinations', as it will be more descriptive: 2. Packs with products does not follow "Calculate pack quantities automatically based on available quantities of items in pack": 3. Related to 1. - I see that the 'Product variant' in combinations generator is per pack (not showing Product variants for other packs. But can we bump it to the top of the list? And even better can we automatically generate those combinations when pack is saved? In general this will save 3-4 clicks. I'm failing to think of a situation that the merchant will use packs with attributes and will not like toe assign all combinations?! I don't see any conflicts with themes or emails so far.

@daresh, your module is a must. So many options to configure the GPSR compliancy and it is supporting thirty bees natively.

As far as I know - nothing is done in that regard. So if it worked on 1.0.8 you are a lucky person and it should work for you in 1.6 too. But I've never used it and can't advise on how to configure it. I'm using all the rest together with litespeed cache and this is plenty for my sites.

You should not use full page cache exactly as it is not production ready. Turn on every other option on the Performance page and it should suffice even for very busy shops.

I can prep a list with screenshots when we're ready to update the page.

In your product page or in module/theme? If later -you have to modify the module/theme to look for new image format.

If it's hooked only to those 3 hooks @wakabayashi mentioned the module does not minify the html. If I modify the module and hook it to header it minifies the html also. In Minify itself there are options to cache the minified files in APCu or OpCode (and others) but I'm unable to understand how to get this to work with negative knowledge. https://github.com/mrclay/minify/tree/master/lib/Minify/Cache and /** * To use APC/Memcache/ZendPlatform for cache storage, require the class and * set $min_cachePath to an instance. Example below: */ //$min_cachePath = new Minify_Cache_APC();

Is it worth it to minify html in 2025 at all? I can not test how long does it take for my server to generate me the minified html but here is some breakdown with one 'large' live site and one test install. Live site lacks test with html minification. 0x - large live site 1x - test site with module as is 2x - test site with module modification to 'somewhat' minify html. The result is not very good the minified output can be further processed by online tools. Should we even care for those <20% savings between raw zstd and mini zstd?

The module's name is HTML, JS and CSS Minification. I got confused that we always minify HTML and that's why there is no switch in BO.

After you saved your settings with webp did you regenerate the thumbnails for products? When this is done, clear your cache and now you should have webp for all products.

Yes, it's not.

First of all. Did you try gradually updating between official major versions and keeping their requirements in check (like dependencies, php version, extensions, etc.)? I would recommend to try this 1.0.8->1.1.0->1.2.0->1.3.0->1.4.0->1.5.0->1.6.0. This would take more time but you will be able to investigate step by step where things break, where you have to check your hosting configuration, etc. 1.0.8->1.6 is quite a big leap, quite a lot things changed for these years, and on top of that when you have some custom work done to the code which could have messed up the database it's get messy quite fast. Also I would recommend on each step to consult with the release notes for every version so you can expect some things that are changed. You can find those here: https://forum.thirtybees.com/forum/2-announcements-about-thirty-bees/ Install Collect logs module when it's visible for you in the modules catalog (I don't know if it supports 1.0.8) and check what is recorded there. Make a test FO registration, make an order, send an email, cancel an order. If everything is OK and there are no records in Collect logs module proceed to the next version of thirty bees. On each step update the files through Core Updated but don't forget to check if there are table updates too - do those or your system will not work as expected. Now, on to your topics: 1. Did you install a mail transport module when under thirtybees 1.6? This functionality was moved to a module so different methods can be used (the one in PS and thirty bees up until now was unmaintained and obstructed further development of the system). After you install your module and configure it you should also select it for use in Advanced Preferences->Email: 2. If you have migrated your old table to a fresh 1.6 install the order state ids might be different. This is not thirty bees fault, it introduces some default states but this configuration might be modified by each shop and this approach is not recommended when updating. If you use Core Updater this will not be the case. 3. Here is the same - most probably a conflict between your old table records and your new install order state ids. When I cancel an order the stock levels are returned to the previous value. 4. Share your carrier settings, check your zones and your carrier coverage for them. More information would be needed to troubleshoot this.

Tidy module I recommended has cronjobs for clearing image so if you're so dependent on your current setup you can try it. It should clear all 'unlinked' images.

Same here. In theory nothing more should be done, but yes, my source is also not minified and it looks 'human-readable'. But I'm pretty sure this was the case before the extraction. EDIT: You have to have your module active and then in Performance have those settings as follows:

If you already have a theme that you like I would advise to contact datakick and he might have some free time in order to help you out with any bugs that you have. The main issue is always within theme's block cart overrides - which leads to 500. The rest is most probably warnings and deprecations. I'm with Warehouse 3.8.7 (the latest version for PS1.6) and it had some issues, cart one too - but now I'm rocking it on php 8.1 with few warnings and it's making me money. Same - I would like to contact datakick soon in order to work on those issues so I can move to 8.2 and later 8.3 (if nothing big pops up).

I don't know about your importing setup but if you are reusing the products (importing so to update prices, etc) why you simply don't skip the image import on the consecutive tries? Regarding Tidy - yes, I too was concerned about this after the image rewrite but it's is working as expected - it detects the unlinked images and offers them for deletion: Delete unused image files (preview) Unused images found and deleted: 9947 /domain.com/img/p/9/8/3/6/9836-cart_default2x.webp - unused /domain.com/img/p/9/8/3/6/9836-backoffice_product_medium2x.webp - unused /domain.com/img/p/9/8/3/6/9836-medium_default2x.webp - unused /domain.com/img/p/9/8/3/6/9836-large_default2x.webp - unused /domain.com/img/p/9/8/3/6/9836-home_default2x.webp - unused /domain.com/img/p/9/8/3/6/9836-small_default2x.webp - unused /domain.com/img/p/9/8/3/0/9830-large_default2x.webp - unused /domain.com/img/p/9/8/3/0/9830-small_default2x.webp - unused /domain.com/img/p/9/8/3/0/9830-home_default2x.webp - unused /domain.com/img/p/9/8/3/0/9830-medium_default2x.webp - unused /domain.com/img/p/9/8/3/0/9830-backoffice_product_medium2x.webp - unused /domain.com/img/p/9/8/3/0/9830-cart_default2x.webp - unused /domain.com/img/p/9/8/3/3/9833-large_default2x.webp - unused /domain.com/img/p/9/8/3/3/9833-backoffice_product_medium2x.webp - unused

If your newly imported products have new ID (and they should have) they created new image. Thirty bees does not care if it is 1:1 with another image on the filesystem (and it should not care). The issue comes from that when old products are deleted their images stay on the filesystem. Which should not be the case. I can recommend Tidy module to cope with those unlinked old images (it wont clean 'duplicates' but it will clean old unneeded images): https://codecanyon.net/item/prestashop-tidy/18965736 It can also do many more things. JUST always do backups.

How many Opencart or Woocommerce themes are compatible with this? Oh... none?