The flexi cart Concept
The purpose of the flexi cart library is to offer modularised shopping cart features, that allow a developer to pick and choose which features they require, without having to include features that are surplus to the clients requirements.
flexi cart is flexible enough to be used to create simple 10 item ecommerce stores, up to huge online stores rivalling the functionality of ecommerce giants like Magento, Opencart and X-cart. The tools are provided, you just have to put them together.
What flexi cart is not, is an all-in-one out-of-the-box e-commerce solution, you still need to build the structure of the site, flexi cart just adds the ecommerce functionality to that structure. If you build the house, it will do the wiring.
Library File Structure
The complete flexi cart library is controlled via several files, a config file, 3 library files, 3 model files and multiple language files.
- The config file as you would expect controls the entire configuration of flexi cart, defining cart column names, database tables and cart behaviour settings.
The library and model files are separated into 3 operational tasks, offering a 'lite', 'standard' and 'admin' set of tools.
Read the library documentation for further information on flexi carts library files.
- The 'lite' library typically reads data from the cart session or database. It is not used to save data.
- The 'standard' library is primarily used to manage the items and settings of the cart, adding/removing items and updating cart localisation settings based on a users location.
- The 'admin' library contains a variety of helper and SQL CRUD functions to manage data within the cart database tables.
- The language files are used to translate cart status and error messages based on a users location.