Component, Attribute on one product not showing when ordered

[NormanRouxel]

Richard,

In this case Actinic is generating erronous code for the Size drop-down on the 1st product. Your product ref is 05063-812 and the generated SELECT code is <SELECT NAME="v_05063-812_0">.

It should be <SELECT NAME="v_05063-812_1">

Unfortunately I've no idea what's causing this to happen, but perhaps the above details will help someone else to contribute.

[fitnessjunky]

Thanks Norman, I appreciate you taking the time to look at this for me. Lets hope someone has a fix, v8 maybe?

Regards
Richard

[cdicken]

I suggest registering an email support enquiry at http://www.actinic.co.uk/support/register.htm as I think the team will need to look at your snapshot to figure out what is going on.

[Billy]

Problems with Duplicates

I have noticed problem with duplicates as well. I am using Normans Upsell software on V 7.0.6 (very nice piece of code Norman) and have noticed some strange happenings.

It seems that some of the duplicates all work as advertised but others do not. For example, I am selling a soft toy 'Patches & Sprinkles Fillies' (http://www.mad4ponies.com/acatalog/sprinkles.html) and have created a number of duplicates of this product to use as upsells in other products. The first duplicate in:
http://www.mad4ponies.com/acatalog/f..._palomino.html
works fine. However the second and third duplicates do not -
http://www.mad4ponies.com/acatalog/h..._play_set.html
http://www.mad4ponies.com/acatalog/r..._play_set.html

It just adds an empty line into the shopping basket which is very bizarre!!

I checked the forum and saw that there have been a number of problems to do with duplicates. So I compacted the database, deleted the original product, purged the content, and recreated the product from scratch, then tried again. But it still did the same!!!!

So I had a look at the html for the pages to see why one worked and the others did not and found the following:

Just before the text 'Choose a Filly' there is a hidden field. For the page that worked correctly this field reads:
<INPUT TYPE="HIDDEN" NAME="v_1!patch-sprink_2" VALUE="on">

This field is identical in the non-working pages but the v_1! does not tie in with the duplicate number.
So in the other two duplicates I changed them manually from v_1! to:
<INPUT TYPE="HIDDEN" NAME="v_2!patch-sprink_2" VALUE="on">
and
<INPUT TYPE="HIDDEN" NAME="v_3!patch-sprink_2" VALUE="on">
respectively.

I then loaded this manually and tried them out and hey prestoe they worked.
I then checked some of my other duplicates to compare what had been generated, and actinic had done this correctly as shown in my manual amendment above?!?

So my next question is what does this field represent? And why is actinic doing correctly for some duplicates and not others?

Thanks
Mark

[NormanRouxel]

Hi, Mark

The <INPUT TYPE="HIDDEN" NAME="v_3!patch-sprink_2" VALUE="on"> looks like you've got a mandatory component associated with that product. If it was optional you'd have a visible TYPE="CHECKBOX" instead.

As to some items failing to add to Cart (you're weirdly getting an invisible product and the Cart Quantity increases each time), try the following to take the Upsell patch out of the loop.

Take one of these funny Upsell products and change its Template from the Upsell Secondary one and instead make it a normal layout. Don't worry if it messes up the page display. Do a temporarily Upload. Now see if that product still fails to add to Cart properly. If so the problem is in Actinic's creation of the Duplicate, not in the Upsell.

Another way to do this is to copy the Upsell product and paste it somewhere else, again changing it to use a nomal layout. Again upload and see how Add to Cart works.

[Billy]

Thanks Norm. I tried all this without your upsell patch just incase it was that, but as suspected it had nothing to do with your code.

It is purely the way actinic is numbering the duplicates. It seems that it is number one of the properties of the duplicate incorrectly whilst numbering all the other properties of the same duplicate correctly.
This also seems to be happening randomly. I have not managed to figure out why it does it to some products and not others. It also seems that once actinic has decided to do it with one particular product it does it consistantly even if you delete all the duplicates and start again.

I have now noticed it was doing this for a few of my other products and have taken the duplicates off line for now until i resolve the problem.

I have left the above example online for now so that it can be viewed.

Does anyone have any ideas about this???

Thanks
Mark

[Billy]

Does anyone have any idea about this at all??????

Mark

[TraceyG]

Hi Mark,

This looks like it needs further investigation. Can you raise a support query here so that we can get your snapshot to test out.