Page 1 of 1
Multistores, how do the work?
Posted: Tue Sep 07, 2010 4:57 pm
by a110y
I'm new to opencart and I would like to learn more about the implementation (, internals) and usage of the multistore feature in opencart. As far as I understand, it creates another "store" that is administered by a central admin. Thus, although it implements multistore, it lacks a multivendor support. However, are the different website entities (products, categories, customers, etc.) distinct across the stores?
Thank you.
Re: Multistores, how do the work?
Posted: Tue Sep 07, 2010 6:45 pm
by mystifier
Multi-store is a single admin for muliple stores.
The Catalog allows Categories, Manufacturers, Products, Information Pages to be enabled in whichever stores you choose so can contain any mixture of common, store-combination or store-unique ones.
Re: Multistores, how do the work?
Posted: Tue Sep 07, 2010 8:23 pm
by a110y
Interesting. Thank you for the information.
I have a few more questions though, when "shopping" from a multi-store configured site does the payment go to the admin or is the payment information configurable?
Also, when I edit a store (which is not the default store), under the "Options" tab, I see that it alters the options of the default site (I mean they edit the global option instead of altering their local options). Is that the intended behaviour?
Re: Multistores, how do the work?
Posted: Tue Sep 07, 2010 8:51 pm
by mystifier
The Store table is defined as below so they are the available store specific options (many of them set default values).
Code: Select all
CREATE TABLE IF NOT EXISTS `store` (
`store_id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(64) COLLATE utf8_bin NOT NULL,
`url` varchar(255) COLLATE utf8_bin NOT NULL,
`title` varchar(128) COLLATE utf8_bin NOT NULL,
`meta_description` varchar(255) COLLATE utf8_bin NOT NULL,
`template` varchar(64) COLLATE utf8_bin NOT NULL,
`country_id` int(11) NOT NULL,
`zone_id` int(11) NOT NULL,
`language` varchar(5) COLLATE utf8_bin NOT NULL,
`currency` varchar(3) COLLATE utf8_bin NOT NULL,
`tax` int(1) NOT NULL DEFAULT '0',
`customer_group_id` int(11) NOT NULL,
`customer_price` int(1) NOT NULL,
`customer_approval` int(1) NOT NULL,
`guest_checkout` int(1) NOT NULL,
`account_id` int(11) NOT NULL DEFAULT '0',
`checkout_id` int(11) NOT NULL DEFAULT '0',
`stock_display` int(1) NOT NULL,
`stock_check` int(1) NOT NULL,
`stock_checkout` int(1) NOT NULL,
`stock_subtract` int(1) NOT NULL,
`order_status_id` int(11) NOT NULL,
`logo` varchar(255) COLLATE utf8_bin NOT NULL,
`icon` varchar(255) COLLATE utf8_bin NOT NULL,
`image_thumb_width` int(5) NOT NULL,
`image_thumb_height` int(5) NOT NULL,
`image_popup_width` int(5) NOT NULL,
`image_popup_height` int(5) NOT NULL,
`image_category_width` int(5) NOT NULL,
`image_category_height` int(5) NOT NULL,
`image_product_width` int(5) NOT NULL,
`image_product_height` int(5) NOT NULL,
`image_additional_width` int(5) NOT NULL,
`image_additional_height` int(5) NOT NULL,
`image_related_width` int(5) NOT NULL,
`image_related_height` int(5) NOT NULL,
`image_cart_width` int(5) NOT NULL,
`image_cart_height` int(5) NOT NULL,
`ssl` int(1) NOT NULL,
`catalog_limit` int(4) NOT NULL DEFAULT '12',
`cart_weight` int(1) NOT NULL,
PRIMARY KEY (`store_id`)
)
There is only one payment link which is a big failing for me too. My post here was unanswered but I think it will be a case of adding fields to the [Store] table and using them in a payment module instead of entries in [Setting] table.
I may have to cross this bridge myself soon.