lukeryan Posted April 24, 2013 Posted April 24, 2013 Hi there, Our oscommerce site has been up and running for a while but something changed today on the site maybe as a result of another code alteration. We've got a heavily re-designed oscommerce store. Bascially on our product listing page (see here: http://www.partybritain.com/womens-fancy-dress-tv-film-characters-c-2_28.html) the buy now button (which we have changed the graphic to say more) is displaying twice. I am really puzzled as to why this has only just started to happen and can't seem to find the root of the problem anywhere so any help would be much appreciated! I have attached the file includes/modules/product_listing.php as this is where most of the work is done for this page. Please help as this is on our live website! Kind regards, Luke product_listing.php
♥GLWalker Posted April 24, 2013 Posted April 24, 2013 What happens if you set the buy now to 0 in the admin under configuration/product listing? Follow the community build: BS3 to osCommerce Responsive from the Get Go! Check out the new construction: Admin Gone to Total BS!
♥joli1811 Posted April 24, 2013 Posted April 24, 2013 Hi, Could this be coming from index.php ? Really not sure. To improve is to change; to be perfect is to change often.
lukeryan Posted April 26, 2013 Author Posted April 26, 2013 Thanks for the replies. WebSource 5 when I set the buy now column to 0 the price appeared twice instead on the product listing page. I have in the meantime asked for some other help from someone I know and he suggested adding the below line after line no. 54 in product_listing.php if ($column_list[$col] == 'PRODUCT_LIST_SORT_ORDER'){break;} so that it is above switch ($column_list[$col]) { case 'PRODUCT_LIST_MODEL': $lc_align = ''; $lc_text = ' ' . $listing['products_model'] . ' '; break; On testing this has seemed to solve the problem. As I'm not great with programming do you think this coding is a good solution to the issue? Regards, Luke
Recommended Posts
Archived
This topic is now archived and is closed to further replies.