Product Problem - Buy Now Function

[zmsan]

Somehow when I am in the long list of products and I click buy it now - or a link like the one below - it goes to the product detail page and does not act like it should in the "buy it now" form (going to the checkout page etc)

 

Is there something in a file I can change? I have been searching in php files for the action=buy_now or something that would lead me there. Somehow maybe I set it to go to a product detail page? I can't find anything in index.php.

 

www.site.com/catalog/index.php?cPath=1_2&sort=2a&action=buy_now&products_id=9

 

Thanks for any help!

[zmsan]

Anyone please?

[Guest]

What, if any modifications have you made to the files?

Have you tried this with several different products? Do you have inventory of the items (are they in stock in your store?)

[kymar]

I'm currently researching the same problem - of buy now, when chosen from a product_listing or related column - sometimes calls the shopping cart, sometimes goes to the product_info page.

 

I only just noticed the problem now after having installed many modifications, so it would be better for a number of reasons, I think, to get to an understanding of how buy now is supposed to work rather than trying to get back to whatever last consistently functional state there might have been. For all I know, this problem has been around for a while, and I only just noticed it.

 

Outwardly, the set-ups appear identical, though all of the items in one category seem to be working fine. In another category, some items work as desired, some don't - even items that appear right next to each other. Oddly, items that have a few apparently irrelevant characteristics in common all seem to work in the same way Thus all items of one sub-type work as desired, but all items of a different sub-type (though in the same category and otherwise identical in appearance) fail to work.

 

I think I'm looking at some peculiar interaction between characters embedded on the one hand in the item descriptions or in other details and on the other in the "buy now" code or product_listing formatting code.

[kymar]

Well, I can't say I understand it yet, but I think I've narrowed down the problem a bit.

 

It seems that buy now on items added after a recent change to the database (addition of a new field) function correctly. Buy now is dysfunctional on items that were in the catalog prior to the change - even though they have since been updated to incorporate the new field. Buy now functions properly on an item that I deleted, then added again.

 

Where the problem lies - with the database tables, with EasyPopulate, with some aspect of the New Fields code, or with some other interaction or error - I still don't know.

[zmsan]

I think I have figured out that it will not go to buy now if there are product attributes - because people actually have to select the attributes. So, it's ok how it is it turns out.

[kymar]

I think I have figured out that it will not go to buy now if there are product attributes - because people actually have to select the attributes. So, it's ok how it is it turns out.

Well - maybe that works for you in your set-up, but all of the items I've been having this problem with have identical attributes - currently "n/a." (Actually, product attributes are a waste of space for me, but that's another topic - one of these days I'll get around to deleting everything related to them).