Yeah, I'll file a bug so that we can get to this when there's time. For
my part, I can provide a temporary patch which will solve the problem
for everyone - and truthfully - at the moment I can't think of anything
else that will fix it since the ProductAssociation is associating
products - not categories.
Therefore there can be no context on where these other products might
live. We could always look up the categories that these products come
from and just pick one of the potentially valid categories, but is that
better than taking them to a product page without an active category?
Cheers,
Tim
David E. Jones wrote:
That's an interesting re-use side-effect bug... I guess we could
either create a separate ftl file for the cross/up/etc-sells than the
one used for the category listings, or we could make the current one
more intelligent to know where it is being included from. Either way
is fine by me...
-David
On Aug 10, 2006, at 3:22 PM, Tim Ruppert wrote:
Are rendered using the productsummaryScreen - which is normally
fine. I found something strange when my products starting showing up
in multiple categories.
Picture Products A, B, & C which are all in the Coat Category. So,
you associate these as product_complements and when you're in the
Coat Category the URLs to the Suggested Products look something like
/ecommerce/control/crosssell/~category=100/~product_id=10000 - (let's
say this is to Product C). Let's say that A has the associated
products B & C, and the like for each of the others.
This is awesome, but what happens when you place A & B on special and
they show up on your main page? Well, then the detail page looks the
same except the URLs look like this
/ecommerce/control/crosssell/~category=SPECIALS/~product_id=10000 .
This is a problem because C is not actually in the SPECIALS - and
causes an error. I have fixed this by using a different
productsummaryScreen that removes the ~category component from the
URL - which is kinda weird, but it works.
Is this something we should fix in OFBiz?
