e-commerce

I am looking to create a MySQL shop that is capable of handling multiple categories. I have all of the category facility etc sorted but the bit I am not getting anywhere with is this.. Each item can have multiple options, for example a T-Shirt should have the options 'Colour' and 'Size'. I then need to create a number of variations/ derived products from the parent product specifying that an Extra Large Blue T-Shirt has 20 in stock (for example). The problem is, it's not just clothes being sold, it could be any number of things. So I also need this schema to be able to handle an infinite

I'm not much of a frontend guy, just learning jQuery, so any help is appreciated. What's the easiest, most stable jQuery zoom plugin? I have a regular size product image and a detailed image. I need to be able to zoom in somehow. Which would you recommend? jqzoom fancyzoom See also: Anything Zoomer Magnify Mag View Whole bunch of them check CloudZoom: the best, imo http://www.professorcloud.com/mainsite/cloud-zoom.htm check AJAX-ZOOM: http://www.ajax-zoom.com/index.php?cid=examples What about zooma? Check it here: http://plugins.jquery.com/project/zooma 来源： https://stackoverflow.com/questions

I'm searching for a lightweight e-Commerce web-application implemented in PHP5 and using MySQL as storage db. main requirements are: as small as possible Free or Open Source supporting multi-language (best if utf-8 was primarily supported) easy to use (don't need core to be bloated with functionality I won't use) basic system for setting up prices, multi-language strings and images small overhead on server fast to deploy Please don't recommend Magento as I found it a little bloated for the functionality I'm looking for. looking forward for your tips / recommendation On OpenSourceCMS you can

I am using magento for a time now. I wanted to know is it possible to enable Cash On Delivery option for admin use only. I want to use it as Store Pickup... So this way manual orders can be only created in admin panel for those who want Store Pickup. I dont want this to be shown in Magento Frontend Store. Can you all help me out ??? Joseph at SwiftOtter There are a number of ways to achieve this, but they require a familiarity with the Magento ecosystem. I would discourage using CSS to hide it from the end user, because someone that was slightly knowledgeable about CSS could easily unhide it

We are actively developing modules and when we push the changes to our production site, there are usually several configuration changes we need to make. Would be nice to automate this...thoughts? Not sure if it is still actual, but if you mean changes to system -> config, then it is much more better to use such config.xml nodes instead of writing database upgrade. Magneto processes core_config_data table into global XML structure, so you may just change XML structure without using db table for making changes to system configuration. Here is small example: <config> <stores> <french> <design>

I am writing an ecommerce site, and need a good way to calculate product variations. The Site has products, products can have many option groups, option groups can have many options. So a Tshirt Product has 3 option groups and options: Size : Small, Medium, Large, Color : Red, Blue, Yellow, Black, Material : Cotton, Nylon, which creates: small red cotton, small red nylon, small blue cotton, small blue nylon, ... so on and so forth I know that the script below works, but also that it can be optimized. Can anyone furnish a better working example of this? It should be possible using recursion as

Where should I store shopping cart data in session or in database? (I think in amazon.com shopping cart after user logout and after month login again his orders that he choose in shopping cart saved) Thanks, Yosef Musa Of course shopping cart data is a critical data. Where to save this data it depends on that user which your e-commerce system works. With Not Signed (yet) users - You have to save this data on web storage, html5 gives you ability for this.Simple using Front End Storage, which equips any Browser (Cookie, Session Storage, Local Storage). On checkout process system must require