the.rampage.rado

If you use Warehouse it's breadcrumbs.tpl emits schema. If you use the JSON module (which is complete; very few items are to be improved/added to it), you will have 2 fields for breadcrumbs. Which is not correct but is not problematic; I ran my shop until recently that way and only noticed and removed the schema from the tpl last month. The discovered rich snippets in Webmaster Tools started dropping and normalized to the correct level (from double the amount previously). I recommend using the JSON module as it offers other data for the whole shop too.

Claude/Codex will change few lines of code, not create entiran ely new module for you. But that way you will be able to update your shop, have many security patches, performance gains, etc.

Does it work with non ASM products too? Previously I expereinced an 'issue' with it where I had mixed catalog (ASM and non-ASM) products in the cart and it made split orders for thast cart. But how i works for non-ASM carts? I believe the products have to be set to use different carriers prior to creating the cart/order? But in this case the functionality @DRMasterChief proposed (option to change delivery method post-order) will not be available through the split-order?

What if you ask the customer post-order and they give you permission by email? I see no harm in that if you receive it.

My initial approach was flawed. I might revisit this later. Your idea is good. We should have this functionality in the core, not as a module, as this scenario is possible for every merchant.

Yes, I had similar issues with Warehouse theme and other modules. Codex and, before that, chatgpt fixed them and, I was able to migrate from php 7.4 to 8.3 in like 2 months. The 20 USD account per month is worth every penny for small merchants.

What is the issue with this module? If you're hacked, first you'll have to find the compromised files, clean/restore them, then look through access logs to find from where did they gained access. The only solution is to patch the hole, but since 1.4 there were numerous security flaws fixed.

The BO htaccess section is little buggy. Add this through FTP instead. You'll notice you've added it and it's there in the file but it does not always show in BO preview.

Please, update your shop to the latest version. If this does not solve the issue you should find some access logs, investigate if something is changed and gives access to somebody, etc. As a start - use code updater to compare against 1.4 official and check every file it finds that is different.

Hope this helps: https://github.com/thirtybees/thirtybees/pull/2132

It would be perfect, but it needs a lot of work.

Thank you for the detailed explanation, Petr! I did not see that the old behaviour is moved in the old pack. I will test it now. You said you fixed the pack not depleting the product quantity bug when configured, right? Regarding the second approach, I think I get it now - we select first the attributes in the said combination and then we configure the applicable products for the said combination. Adding them one by one. Then add second combination, and repeat. I will experiment with it. For now one bug I see with the old behaviour (normal pack and virtual attribute) is that it does not calculate the available quantity for the pack based on the product availability: Also, do we consider if the product is 0 (or has negative stock due to previous preorders) but is WOO: Allow orders - does the pack treat this as an orderable state for the pack also?

Did you try the module and the options it gives you? In general if you migrated from Warehouse you will see that Niara is far less configurable.

Could somebody that have already updated or tested the new implementation give me some guidance on how to use the new feature? The old implementation was quite intuitive. I can't understand how to implement the new approach. I have to select Packs with combinations, don't save and directly go to Combinations -> New combination and add my products, but then what? In the same time I have to add attributes, but how? Quite unintuitive. My use case is packs of products with combinations, only 1 product per combination, but with sizes. Like 5x or 10x balls packs. Later, I would like to use it to make packs of sporting kits (shirt and pants) - with 2 attributes - color and size. But how? I even tried asking the bot - it was unable to give me detailed description I can follow... 😞

You got a PM.