R8 Custom Field Display Mismatch - Potential Bug or?

For general questions and discussions specific to the AbleCommerce GOLD ASP.Net shopping cart software.
Post Reply
VIPER7
Captain (CAPT)
Captain (CAPT)
Posts: 247
Joined: Fri Apr 15, 2005 2:49 pm

R8 Custom Field Display Mismatch - Potential Bug or?

Post by VIPER7 » Fri Aug 01, 2014 10:04 am

Ok, let's see if I can accurately depict what's going on here. I think we may have some sort of potential bug when displaying custom field info in the cross selling efforts in a product display.

Go to this product my website:

http://www.drumcityguitarland.com/Schec ... 10505.aspx

Then, access the "Also in HELLRAISER Collection" tab.

Note the first product on the left, says "Availability: Coming Soon" (our custom field). Then, click on that product to go to it's full page display (will take you here > http://www.drumcityguitarland.com/Schec ... 10501.aspx)

We have since updated the Availability of this product and as such is displaying accurately in the full product listing view. However, the custom field display in the cross sell tab seems to be static and thus is incorrect. Is there something we need to do to update all cross sell info across the site? Does this make sense?

Thanks as always for any insight as to what's going on here!

User avatar
Katie
AbleCommerce Admin
AbleCommerce Admin
Posts: 2651
Joined: Tue Dec 02, 2003 1:54 am
Contact:

Re: R8 Custom Field Display Mismatch - Potential Bug or?

Post by Katie » Sun Aug 03, 2014 7:22 am

It looks like a caching issue. Have you tried refreshing your browser? If that doesn't work, you could try recycling the application pool.
Thank you for choosing AbleCommerce!

http://help.ablecommerce.com - product support
http://wiki.ablecommerce.com - developer support

VIPER7
Captain (CAPT)
Captain (CAPT)
Posts: 247
Joined: Fri Apr 15, 2005 2:49 pm

Re: R8 Custom Field Display Mismatch - Potential Bug or?

Post by VIPER7 » Sun Aug 03, 2014 8:16 am

Hi Katie, I have tried accessing the site / page in question on new computers that have never been to the site before and get the same results. Recycling the app pool had no effect either. Any other suggestions as to what might be going on here? Thanks!

User avatar
Katie
AbleCommerce Admin
AbleCommerce Admin
Posts: 2651
Joined: Tue Dec 02, 2003 1:54 am
Contact:

Re: R8 Custom Field Display Mismatch - Potential Bug or?

Post by Katie » Sun Aug 03, 2014 8:25 am

What search provider are you using? If it is Lucene, then you might try reindexing the database. Go to Website > Indexes to do this.
Thank you for choosing AbleCommerce!

http://help.ablecommerce.com - product support
http://wiki.ablecommerce.com - developer support

VIPER7
Captain (CAPT)
Captain (CAPT)
Posts: 247
Joined: Fri Apr 15, 2005 2:49 pm

Re: R8 Custom Field Display Mismatch - Potential Bug or?

Post by VIPER7 » Sun Aug 03, 2014 10:18 am

I guess I am using the SQL search provider, since when I go to this page I get the following:

Index maintenance is not necessary when you are using the SQL search provider.

User avatar
Katie
AbleCommerce Admin
AbleCommerce Admin
Posts: 2651
Joined: Tue Dec 02, 2003 1:54 am
Contact:

Re: R8 Custom Field Display Mismatch - Potential Bug or?

Post by Katie » Sun Aug 03, 2014 11:07 am

Did you notice that viewing the "Also in" tab for this product: http://www.drumcityguitarland.com/Schec ... 10501.aspx will show you Availability of "in stock today". It seems like the custom field information being output in the "Also in collections" are showing the field information for the product being viewed.

Do you want to check your code to see if that is the cause?

Is it sad that we are both working on a Sunday :)
Thank you for choosing AbleCommerce!

http://help.ablecommerce.com - product support
http://wiki.ablecommerce.com - developer support

VIPER7
Captain (CAPT)
Captain (CAPT)
Posts: 247
Joined: Fri Apr 15, 2005 2:49 pm

Re: R8 Custom Field Display Mismatch - Potential Bug or?

Post by VIPER7 » Sun Aug 03, 2014 2:05 pm

Hello Katie,

I believe you are correct in ALL regards: A) After further investigation and thought, the bug is in MY code, not AC and B) it IS sad we are working on a Sunday. :) Let's pick this back up again tomorrow! ;)

Post Reply