Help for Aimeos

Hello! Is there any setting so that whenever someone adds a product to the basket that's already in the basket, or increases the amount of it, it doesn't increase the quantity but adds a different entry to the basket? In other words, I need a basket that doesn't aggregate the same products into a si...

Yes, that's the goal. Multiple categories would be an issue, but in that case I guess you just pick one and move up the parent list up to level 0 (since categories can't have more than one parent as far as I can tell). Or maybe display multiple breadcrumbs, say, up to 3 if there are that many catego...

Actually I left it out, if you open a product's detail page directly, the breadcrumbs area simply displays 'search results'.
So yeah, it is buggy, breadcrumbs should display the full path to the current page regardless of where or how you arrived to the page.

Hello! There seems to be a bug with the way breadcrumbs are handled, I'm using Laravel 5.1 but I think it's an unrelated aimeos issue. If I navigate to a product in a regular fashion, that is first selecting a category, then a product, it works fine. If I then go to a different category, and select ...

Well that's not very optimal.. I actually need the original rebate value when doing coupon calculations, since there will be product rebates, coupons, and discounts (for which I'm using coupons), and of all these, only one should be actually applied, the one which gives the greatest rebate, and the ...

Thanks, will try it out!

Took a little longer than expected to set up an alternate site for testing, and sadly, I don't see any changes :( dump($product->getPrice()->getRebate()); dump($product->getPrice()); still yields "0.00" Standard {#1031 ▼ -values: array:19 [▼ "price.id" => "1537" "p...

We tried monkeying around with those before, and came to the same conclusion, it should not happen that there are two properties under the same name. Renaming $values to $basevals creates an error so majestic it breaks somewhere along the lines of setting up basic site data: Exception in Standard.ph...

Yet it returns "0.00". Nevermind, I set the getRawValues function on the MShop\Common\Item\Base to public, it returns the correct values. As I see it nothing actually uses that function so it should be okay.

The problem is not even really with the rebate value being protected, the problem is that a Price object holds 2 "values", which are different properties that actually share the same name, and there is a discrepancy between their values. Some digging revealed this to be the result of them ...