major flaw in components and attributes

[Simpsons]

Having spent allot of time creating products with multiple permutations, it has now emerged that Actinic is incapable of 'shipping and handling' products that utilise attributes and components.

Although Actinic is capable of calculating an appropriate carriage charge, having downloaded your orders and selected the 'shipping and handling' tab (in your orders area), you'll see all proposed packages are empty.

The only way around this problem is to use 'Sum of Product and Component Prices' in your pricing model. However, this approach creates a double entry in the shopping cart, one for the visible product and one for the hidden selected component, which can be confusing to customers.

Please can Actinic Support tell me if there's away around this infuriating problem.

Many thanks in advance.
Kevin Simpson

[wjcampbe]

Kevin,
There is a work around posted on this forum that allows you to list the components, but does not show a quantity against them to avoid customer confusion. Would that help you?

[Simpsons]

Bill

At this stage, and so close to launch, I'll consider any feasible solution.

Thanks
Kevin

[cdicken]

Hi Kevin & Bill (and anyone else reading this)

Just for reference, the details of the Perl change required to remove the component quantities from appearing in the shopping cart are detailed in this knowledge base article

[Simpsons]

Chris,

Thanks for this. I taken a look at ActinicOrder.pm and there's only one instance of "$pComponent->{'QUANTITY'}," throughout the entire script. Your knowledgebase article says there's two and to only change the first.

What do you suggest?

Thanks
Kevin

[cdicken]

How odd - I found two. They are quite close to each other.

THe one you want to edit is within the following code block:

		foreach $pComponent (@aComponentsIncluded)
			{
			$ProdTable .= ProductLineHTML($pComponent->{'REFERENCE'},
													$pComponent->{'NAME'} . $pComponent->{'DDLINK'},
													$pComponent->{'QUANTITY'},
													$sProductLineHTML);
			}

[Simpsons]

Thanks for clarifying this, I've now tried it and it's made no difference what so ever.

I presume this change is designed to show both the product and an associated component in the shopping cart with no quantity shown against the component entry?

If this is the case, what happens in relation to component pricing? If component quantity is ignored does Actinic still know to charge the component price? Or is it opting for the product price?

I feel a can of worms in about to be opened!

Kevin

[jeff p]

It calculates the component prices correctly it just doesn't display the repetitive quantity figures and cleans up the cart a bit.